You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Davanum Srinivas <da...@gmail.com> on 2004/07/22 04:39:58 UTC

Re: DeserializationContextImpl.getDeserializerForClass():490 - No deserializer for java.lang.Object

do you have a stack trace? please post a bug to JIRA.

thanks,
dims

On Wed, 21 Jul 2004 13:19:52 -0700, Peter Molettiere
<pi...@axonstudios.net> wrote:
> 
> After upgrading to the latest CVS source, we're noticing a new error
> being thrown by axis during the execution of our app.
> 
> DeserializationContextImpl.getDeserializerForClass():490  - No
> deserializer for java.lang.Object
> 
> One of the classes we register a type mapping for has a bean property
> which returns a java.lang.Object, and it looks like this is causing the
> complaint. In most cases, this property returns one of the other
> classes we've already set type mappings for, however, sometimes it is
> not used, and is not set.
> 
> The only change we've made to our code to cause this new error is
> upgrading axis, so I wanted to ask if someone knows of a change in the
> last beta (latest cvs source) which would cause this error, and if
> there's a recommended solution.
> 
> Our possible solutions at this point include setting a serializer for
> java.lang.Object, or ignoring the error, as it doesn't seem to actually
> cause any badness, aside from the error message.
> 
> --Peter
> 
> 


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

Re: DeserializationContextImpl.getDeserializerForClass():490 - No deserializer for java.lang.Object

Posted by Peter Molettiere <pi...@axonstudios.net>.
Jira bug filed:
http://nagoya.apache.org/jira/browse/AXIS-1471

--Peter


On Jul 21, 2004, at 8:28 PM, Peter Molettiere wrote:

>
> Here's a trace, bug in jira coming up:
>
> java.lang.NoSuchMethodException:  
> java.lang.Object.getDeserializer(java.lang.String, java.lang.Class,  
> javax.xml.namespace.QName)
> 	at java.lang.Class.getMethod(Class.java:978)
> 	at  
> org.apache.axis.encoding.DeserializationContextImpl.getDeserializerForC 
> lass(DeserializationContextImpl.java:481)
> 	at  
> org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserial 
> izer.java:250)
> 	at  
> org.apache.axis.encoding.DeserializationContextImpl.startElement(Deseri 
> alizationContextImpl.java:1008)
> 	at  
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java 
> :159)
> 	at  
> org.apache.axis.message.MessageElement.publishToHandler(MessageElement. 
> java:838)
> 	at  
> org.apache.axis.encoding.DeserializerImpl.startElement(DeserializerImpl 
> .java:373)
> 	at  
> org.apache.axis.encoding.ser.BeanDeserializer.startElement(BeanDeserial 
> izer.java:130)
> 	at  
> org.apache.axis.encoding.DeserializationContextImpl.startElement(Deseri 
> alizationContextImpl.java:1021)
> 	at  
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java 
> :159)
> 	at  
> org.apache.axis.message.MessageElement.publishToHandler(MessageElement. 
> java:838)
> 	at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:198)
> 	at org.apache.axis.message.RPCElement.getParams(RPCElement.java:323)
> 	at org.apache.axis.client.Call.invoke(Call.java:2418)
> 	at org.apache.axis.client.Call.invoke(Call.java:2317)
> 	at org.apache.axis.client.Call.invoke(Call.java:1774)
>        [our application code removed from trace]
>
> --Peter
>
> On Jul 21, 2004, at 7:39 PM, Davanum Srinivas wrote:
>
>> do you have a stack trace? please post a bug to JIRA.
>>
>> thanks,
>> dims
>>
>> On Wed, 21 Jul 2004 13:19:52 -0700, Peter Molettiere
>> <pi...@axonstudios.net> wrote:
>>>
>>> After upgrading to the latest CVS source, we're noticing a new error
>>> being thrown by axis during the execution of our app.
>>>
>>> DeserializationContextImpl.getDeserializerForClass():490  - No
>>> deserializer for java.lang.Object
>>>
>>> One of the classes we register a type mapping for has a bean property
>>> which returns a java.lang.Object, and it looks like this is causing  
>>> the
>>> complaint. In most cases, this property returns one of the other
>>> classes we've already set type mappings for, however, sometimes it is
>>> not used, and is not set.
>>>
>>> The only change we've made to our code to cause this new error is
>>> upgrading axis, so I wanted to ask if someone knows of a change in  
>>> the
>>> last beta (latest cvs source) which would cause this error, and if
>>> there's a recommended solution.
>>>
>>> Our possible solutions at this point include setting a serializer for
>>> java.lang.Object, or ignoring the error, as it doesn't seem to  
>>> actually
>>> cause any badness, aside from the error message.
>>>
>>> --Peter
>>>
>>>
>>
>>
>> -- 
>> Davanum Srinivas - http://webservices.apache.org/~dims/

Re: DeserializationContextImpl.getDeserializerForClass():490 - No deserializer for java.lang.Object

Posted by Peter Molettiere <pi...@axonstudios.net>.
Here's a trace, bug in jira coming up:

java.lang.NoSuchMethodException:  
java.lang.Object.getDeserializer(java.lang.String, java.lang.Class,  
javax.xml.namespace.QName)
	at java.lang.Class.getMethod(Class.java:978)
	at  
org.apache.axis.encoding.DeserializationContextImpl.getDeserializerForCl 
ass(DeserializationContextImpl.java:481)
	at  
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeseriali 
zer.java:250)
	at  
org.apache.axis.encoding.DeserializationContextImpl.startElement(Deseria 
lizationContextImpl.java:1008)
	at  
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java: 
159)
	at  
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j 
ava:838)
	at  
org.apache.axis.encoding.DeserializerImpl.startElement(DeserializerImpl. 
java:373)
	at  
org.apache.axis.encoding.ser.BeanDeserializer.startElement(BeanDeseriali 
zer.java:130)
	at  
org.apache.axis.encoding.DeserializationContextImpl.startElement(Deseria 
lizationContextImpl.java:1021)
	at  
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java: 
159)
	at  
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j 
ava:838)
	at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:198)
	at org.apache.axis.message.RPCElement.getParams(RPCElement.java:323)
	at org.apache.axis.client.Call.invoke(Call.java:2418)
	at org.apache.axis.client.Call.invoke(Call.java:2317)
	at org.apache.axis.client.Call.invoke(Call.java:1774)
        [our application code removed from trace]

--Peter

On Jul 21, 2004, at 7:39 PM, Davanum Srinivas wrote:

> do you have a stack trace? please post a bug to JIRA.
>
> thanks,
> dims
>
> On Wed, 21 Jul 2004 13:19:52 -0700, Peter Molettiere
> <pi...@axonstudios.net> wrote:
>>
>> After upgrading to the latest CVS source, we're noticing a new error
>> being thrown by axis during the execution of our app.
>>
>> DeserializationContextImpl.getDeserializerForClass():490  - No
>> deserializer for java.lang.Object
>>
>> One of the classes we register a type mapping for has a bean property
>> which returns a java.lang.Object, and it looks like this is causing  
>> the
>> complaint. In most cases, this property returns one of the other
>> classes we've already set type mappings for, however, sometimes it is
>> not used, and is not set.
>>
>> The only change we've made to our code to cause this new error is
>> upgrading axis, so I wanted to ask if someone knows of a change in the
>> last beta (latest cvs source) which would cause this error, and if
>> there's a recommended solution.
>>
>> Our possible solutions at this point include setting a serializer for
>> java.lang.Object, or ignoring the error, as it doesn't seem to  
>> actually
>> cause any badness, aside from the error message.
>>
>> --Peter
>>
>>
>
>
> -- 
> Davanum Srinivas - http://webservices.apache.org/~dims/