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
