Hi all I have developed some WebServices using Axis...nothing big...just a couple of examples serializing beans and so between a java (Axis) server and a java client...however...now a project is arising where web services is going to be used in large scale...
and to add even more complexity..the web services deployed must be consumable by other platforms...first case is .NET I have read "inteop" guides in both "camps", ie Java/Axis/J2EE and .NET..In the .NET camp they favor on style of messages and claim that this is according to the WS-Basic profile...So it makes me wonder...how is Axis support for this style (can't remember if it is doc/literal or rpc/literal) ? In the .NET guides, thet also say that one must define the schemas first? Why...? Because a schema can be understood by both sides? or to define the message structure as they seem to favor message style instead of rpc style? The primary goal of the web servcices developed is to be consumable by many platforms...first two targets is .NET and Axis...more coming.... Any thoughts, ideas....Anne, please...you seem to have done a lot in this fields.. Best regards Henrik
