|
Re: What Are Your Java Pain Points, Really?
|
Posted: Feb 15, 2007 6:19 PM
|
|
> If they are providing the code, they should be providing > the interface. How does dynamic binding help with this? > You still need to map their method names and structures > s to yours and vice versa with dynamic binding.
Ah well, at the risk of being tedious:
The problem is that If an interface is defined in product A, and product B doesn't consume A, then B can't provide components that conform to the interface. However, B could provide components that support the same APi (though not formally). Compile-time checking the API against an interface makes things quite awkard in this and similar situations.
As you point out, there needs to be agreement (though this can be after the fact) on method names, though typically such methods would have arguments (if any) of common Java types (e.g., Object, String, Map, List, int, float, etc.), so structure would not enter into the picture.
|
|