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 "Jeff Randolph (JIRA)" <ax...@ws.apache.org> on 2005/03/04 22:22:48 UTC

[jira] Created: (AXIS-1840) RPCHandler cannot find deserializer

RPCHandler cannot find deserializer
-----------------------------------

         Key: AXIS-1840
         URL: http://issues.apache.org/jira/browse/AXIS-1840
     Project: Axis
        Type: Bug
  Components: Serialization/Deserialization  
    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 contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXIS-1840) RPCHandler cannot find deserializer

Posted by "Jeff Randolph (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS-1840?page=comments#action_60375 ]
     
Jeff Randolph commented on AXIS-1840:
-------------------------------------

I tried with the latest CVS version today and got the same of error (cannot find deserializer) without my RPCHandler fix.

> RPCHandler cannot find deserializer
> -----------------------------------
>
>          Key: AXIS-1840
>          URL: http://issues.apache.org/jira/browse/AXIS-1840
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     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 contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXIS-1840) RPCHandler cannot find deserializer

Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS-1840?page=comments#action_60900 ]
     
Davanum Srinivas commented on AXIS-1840:
----------------------------------------

Can you please submit a small test for me to recreate the problem? (and helps ensure that no one breaks the "fix")

thanks,
dims

> RPCHandler cannot find deserializer
> -----------------------------------
>
>          Key: AXIS-1840
>          URL: http://issues.apache.org/jira/browse/AXIS-1840
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     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 contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXIS-1840) RPCHandler cannot find deserializer

Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS-1840?page=comments#action_60246 ]
     
Davanum Srinivas commented on AXIS-1840:
----------------------------------------

Jeff,

we've reworked a lot of the typemapping stuff between RC2 and RC3. Can you please try using RC3 and let us know.

thanks,
dims

> RPCHandler cannot find deserializer
> -----------------------------------
>
>          Key: AXIS-1840
>          URL: http://issues.apache.org/jira/browse/AXIS-1840
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     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 contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira