axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anderson Jonathan" <>
Subject RE: Need suggestions on web service interlope and design
Date Wed, 14 Apr 2004 15:57:02 GMT

Axis 1.2 beta is out...

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

Somebody should really open a Service Oriented Architect school.  :)

Jonathan Anderson
Booz Allen Hamilton

-----Original Message-----
From: HG []
Sent: Wednesday, April 14, 2004 10:20 AM
Subject: Re: Need suggestions on web service interop and design


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

Best regards


----- Original Message -----
From: "Anne Thomas Manes" <>
To: <>
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,
> 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
> 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 []
> Sent: Wednesday, April 14, 2004 3:43 AM
> To:
> 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
> 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
> the .NET camp they favor one style of messages and claim that this is
> according to the WS-Basic profile...So it makes me is Axis
> support for this style (can't remember if it is doc/literal or
> ?
> 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
> The primary goal of the web servcices developed is to be consumable by
> platforms...first two targets is .NET and Axis...more coming....
> Any thoughts, ideas....Anne, seem to have done a lot in this
> fields..
> Best regards
> Henrik

View raw message