I have run into a problem that I have solved but am not pleased with the solution. I have an API that I have written a web service skin for. Here is the general idea:
The 2 API's reference a rate object found in common. This works without a hitch as far as the API's are concerned. When I use the rate object in the services layer, both services expose a rate object from the WSDL. In the web app that uses the services I get an ambiguous reference compile error. I can qualify the call by using QuoteService.Rate, but the question is which one should I use?
The reason I have 2 services - there are actually more - is because the API will be getting quite large. Now we are looking to see if we could refactor into less services and methods, but we would really like a clean, obvious API to be exposed to business partners. As you can see, the qualifying does take some thought also. This is the tip of the iceberg.
At this point I am using the WSDL generated from the asmx files rule the roost. Has anyone come across this situation? If so how have you approached it?