You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Tom Jordahl <to...@macromedia.com> on 2005/02/28 23:38:17 UTC
RE: True/False: Axis *requires* all elements have a deserializer
'registered'?
True.
--
Tom Jordahl
Macromedia Server Development
-----Original Message-----
From: Viens, Stephen [mailto:Stephen.Viens@LibertyMutual.com]
Sent: Thursday, February 24, 2005 10:38 AM
To: axis-dev@ws.apache.org
Subject: True/False: Axis *requires* all elements have a deserializer
'registered'?
A colleague using Axis 1.1 has determined that Axis *requires* that all
elements encountered in the parsing of the message have a deserializer
'registered' with Axis. If a deserializer cannot be found a SAXException is
thrown.
Is this true? Is there a way around this?
We're striving for loose coupling with this service so we don't want the
consumers of our service to be required to regenerate the client-side
artifacts from WSDL when the schema representing the SOAP response is
*extended* .... UNLESS they're interested in the new information.
Steve