Henrik, Axis 1.2 beta is out...
http://archive.apache.org/dist/ws/axis/1_2beta/ Though if you're the adventurous type you can always pull straight from CVS and build it yourself. And yes, we're ALL struggling not only with building WS-I compliant SOAP services, but WS-I complaint SOAP services that fit together into some sort of loosely coupled, scalable, and <gasp> actually useful Service Oriented Architecture. Somebody should really open a Service Oriented Architect school. :) Regards, Jonathan Anderson Booz Allen Hamilton -----Original Message----- From: HG [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 14, 2004 10:20 AM To: [EMAIL PROTECTED] Subject: Re: Need suggestions on web service interop and design Anne, Thanx for the fast info..Just the thing I needed. Now, the task doing schemas first, makes sense..That way you won't get tempted to expose platform specific stuff..Great. Maybe for once in a lifetime I should follow the .NET guides and do things the MS way :-) I can see that Axis 1.2 is alpha...Anyone knows of the beta or final release plans..? Best regards Henrik ----- Original Message ----- From: "Anne Thomas Manes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 14, 2004 3:38 PM Subject: RE: Need suggestions on web service interop and design > Henrik, > > The WS-I Basic Profile disallows the use of SOAP Encoding. It allows only > Document/Literal and RPC/Literal. Technically, WS-I BP doesn't *require* > support for RPC/Literal, though. Microsoft fought long and hard to exclude > RPC-style from the WS-I BP, but they lost that vote. In any case, Microsoft > does not support RPC/Literal, and my guess is that they will never support > RPC/Literal. (Please note, though, that the JAX-RPC specification requires > support for RPC/Literal.) > > If you want to design for interoperability, you should use Document/Literal. > Axis 1.2 provides much better support for Document/Literal than previous > releases. > > I suggest that you follow the .NET guides and define your schema first -- > then generate your beans from the schema. This approach ensures that you > won't attempt to expose Java collections through your WS interface. > > For best interoperability, your interface should consist of simple types, > arrays (defined using minOccurs/maxOccurs), and complex types defined as > sequence structures of simple types, arrays, and/or sequence structures. > > Anne > > -----Original Message----- > From: HG [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 14, 2004 3:43 AM > To: [EMAIL PROTECTED] > Subject: Need suggestions on web service interop and design > > 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 one 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 > >
