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
<[EMAIL PROTECTED]> 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/

Reply via email to