Goran, Thanks for the advice below. Although excellent, I'm debating whether or not to use it in production. Your solution still requires the client to do something fairly intricate - I was hoping to avoid that.
Still, it's a good solution - thanks for walking me through it! Anand On Tue, 29 Jun 2004, [iso-8859-1] Göran Andersson wrote: : > Anand Natrajan wrote: : > : > >Hello! : > >As part of my .NET and Axis interoperability work, I am : > facing a piquant : > >situation. I have written multiple web services using Axis. : > Each of these > >web services defines a particular complex data structure : > called Principal. : <snip> : > When I do so, : > >.NET gives the WSDL a name, somewhat similar to a package : > name in Java. : > >Different WSDLs get different names. However, because of : > this practice, I : > >end up with multiple definitions of Principal viz., : > WSDL1.Principal and : > >WSDL2.Principal. Now, I find I cannot use a single instance : : Hi, : : Select "Show all files" in VS.NET, and set the Custom Tool Namespace on your : Reference.map to the namespace of your choice. That will force VS.NET to : generate the classes in that particular namespace. : Some other interoperability gotchas: : : -You'll get duplicate definitions of the class in the namespace since it is : generated once for each WS. You will have to delete these. : -Don't use inheritance among the entities/DO's in your service, even if the : superclass just contains behaviour and no attributes. You'll have a : nightmare trying to keep track which superclass to delete and how to move : around all the SoapTypeAttribute so that they don't get left behind. If you : forget one SoapTypeAttribute the entity subclass can't be deserialized by : .NET. : : Cheers : /Goran Andersson : : ___________________________________________ : Göran Andersson : Senior Consultant/System Architect : Alcesys AB : +46 733 90 47 10 : mailto:[EMAIL PROTECTED] : : : :
