axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anne Thomas Manes" <>
Subject Re: consequences of choosing axis
Date Tue, 09 Jan 2007 23:57:32 GMT
Sorry for being vague. I was referring to the SOAP platform, not the
underlying servlet/J2EE platform. As I said, Axis2 can be deployed on
any platform. But AXIOM is particular to Axis2. (It is a separate
project, and other SOAP platforms could use it, but to date, the only
other project that I know of that uses AXIOM is Synapse.)

The impact of using a platform-specific object model is that your
client/service code is not portable across other SOAP platforms.


On 1/9/07, ChadDavis <> wrote:
> Anne,
> >One consequence of selecting Axis2 is that it does not [yet] support
> > the standard Java APIs for web services (JAX-RPC and JAX-WS). Axis2
> > uses a platform-specific object model, AXIOM, which is based on StAX,
> > for processing XML. For the most control, you can use the low-level
> > API, which represents message data as an OMElement. But you also have
> > the option of using any data binding system (JAXB, XMLBeans, JiBX,
> > ADB, etc) to convert the XML messages into Java objects for you.
> This may be a dumb question, but what do you mean by platform specific
> object model?  How is AXIOM platform specific?  I'm thinking that its
> all Java so . . . and I don't recall choosing a particular platform
> flavor of the AXIS2 distribution?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message