[
https://issues.apache.org/jira/browse/AXIS-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS-1840.
-----------------------------------
Resolution: Incomplete
> RPCHandler cannot find deserializer
> -----------------------------------
>
> Key: AXIS-1840
> URL: https://issues.apache.org/jira/browse/AXIS-1840
> Project: Axis
> Issue Type: Bug
> Components: Serialization/Deserialization
> Affects Versions: 1.2RC2
> Environment: Windows XP, Java 1.4.2
> Reporter: Jeff Randolph
> Priority: Minor
>
> After running WSDL2Java over a WSDL that used SwA, I was having issues with
> the client code complaining about not being able to find a deserializer for
> my data types when deserializers were clearly registered for them. I found
> that in org.apache.axis.message.RPCHandler.onStartChild(), it was trying to
> find deserializers for this message (or something like it):
> <ns:myElement xmlns:ns="http://blah.com";>
> <myParam>1</myParam>
> </ns:myElement>
> based one of the following:
> 1. {http://blah.com}myElement
> 2. MyElementType.class (if registered) and MyElementType
> 3. MyElementType
> 4. MyElementType.class (if registered)
> But it was not trying:
> {http://blah.com}MyElementType
> I added a check for this and it worked!
> if(dser == null) {
> QName typeWithNS = new QName(namespace, type.getLocalPart());
> deser = context.getDeserializerForType(typeWithNS);
> }
> I would have just submitted a patch but my version currently has other
> changes too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
