ms
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
urce, 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
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 case
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 pro
