Deserialization

[Sudhir]

Title: RE: Apache SOAP 2.3 vs. AXIS

Is there any issue with the use of BeanDeserializer for the service which has a complex return type(returns a java bean) and the operation style is set to "wrapped"(a "document" based service)?   I have set the serializer and the deserializer, but i am getting the deserializer exception. The client I generated looks the same as the one generated by the wsdl2java. Any help is appreciated   Thanks Sudhir The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt. Integrity without knowledge is weak and useless, and knowledge without integrity is dangerous and dreadful. ----- Original Message ----- From: Volkmann, Mark To: '[EMAIL PROTECTED]' Sent: Monday, June 10, 2002 11:17 AM Subject: RE: Apache SOAP 2.3 vs. AXIS Here are a few reasons. I'm sure others can add many more. In my opinion, the first reason is really important! - support for WSDL - support for header mustUnderstand attribute - support for SOAP responses from other toolkits that don't include xsi:type attributes - performance (SAX vs. DOM) - better XML Schema support > -----Original Message----- > From: Mark Hansen [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 10, 2002 9:49 AM > To: AXIS mail list > Subject: Apache SOAP 2.3 vs. AXIS > > > Why would someone choose AXIS over Apache SOAP 2.3 or vice > versa?  What are > the primary differences? *********************************************************************************** WARNING: All e-mail sent to and from this address will be received or otherwise recorded by the A.G. Edwards corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. ************************************************************************************