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. Anne On 1/9/07, ChadDavis <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
