True/False: Axis *requires* all elements have a deserializer 'registered'?

["Viens, Stephen" <St...@LibertyMutual.com>]

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

Re: True/False: Axis *requires* all elements have a deserializer 'registered'?

[Davanum Srinivas <da...@gmail.com>]

You can try using the doAutoTypes flag with latest Axis 1.2 cvs. that
may alleviate the problem.

-- dims


On Thu, 24 Feb 2005 10:38:24 -0500, Viens, Stephen
<St...@libertymutual.com> wrote:
>  
> 
> 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 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/