Re: AXIS serialization/deserialization of XML payloads without SOAP/WSDL processing

[Anne Thomas Manes]

Tony,   Axis MESSAGE style tells Axis that you don't want to use the Axis serialization engine. In this case Axis delivers the contents of the SOAP body directly to the application as a DOM element. Your application can process the XML as it sees fit (e.g., using JAXB).   Note that this style of communication isn't "outside the SOAP processing realm". Axis still implements the SOAP processing model -- it manages the network communications; it creates and manages the SOAP envelope, it processes any SOAP headers that exist; it invokes the appropriate handlers; it loads and manages the application agent for you. The only thing it doesn't do is convert the XML into Java for you.   You might want to do some benchmark comparisons between Axis serialization and JAXB serialization. I'd look at performance, scalability, and footprint differences.   Anne ----- Original Message ----- From: Tony Opatha To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, August 02, 2003 4:51 PM Subject: AXIS serialization/deserialization of XML payloads without SOAP/WSDL processing 1. Is there a way to use AXIS to process and generate XML payload streams using the     XML schema (in .xsd) specifications of the payloads such that the payload streams     are not serialized or deserialized to/from a SOAP message envelope?   2. If AXIS has general schema-driven XML payload serialization and serialization     capability using the payload schema definition than wouldn't this be basically     similar functionality as JAXB?   3. What are step to configure AXIS run-time for such XML payload support outside     the SOAP processing realm? What do we have to design -time to compile     and generate the corresponding serialization/deserialization classes using the     XSD?     Thanks you very much for all your help.   Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software