[xstream-dev] [jira] Created: (XSTR-101) XStream should be able to work with classes that are hot-redeployed

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/XSTR-101

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XSTR-101
    Summary: XStream should be able to work with classes that are hot-redeployed
       Type: Improvement

     Status: Unassigned

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: XStream
   Fix Fors:
             1.0.2

   Assignee: 
   Reporter: Joe Walnes

    Created: Thu, 22 Jul 2004 6:08 AM
    Updated: Thu, 22 Jul 2004 6:08 AM

Description:
Stephane Nicoll wrote:

>Hello list,
>
>We use xstream in Jboss to serialize our messages to XML and post them to JMS
>queues. It works fine (great job) but when we hot redeploy serializable
>classes we have the following exception:
>
>11:10:08,587 ERROR [ejb.plugins.LogInterceptor]
>TransactionRolledbackLocalException in method: public abstract void
>javax.jms.MessageListener.onMessage(javax.jms.Message), causedBy:
>com.thoughtworks.xstream.converters.reflection.ObjectAccessException: Could
>not get field class java.lang.reflect.Field.codAmount: null
>        at
>com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.vis
>itSerializableFields(Unknown Source)
>        at
>com.thoughtworks.xstream.converters.reflection.ReflectionConverter.marshal(Un
>known Source)
>        at
>com.thoughtworks.xstream.core.ReferenceByXPathMarshaller.convertAnother(Unkno
>wn Source)
>        at com.thoughtworks.xstream.core.TreeMarshaller.start(Unknown Source)
>        at
>com.thoughtworks.xstream.core.ReferenceByXPathMarshallingStrategy.marshal(Unk
>nown Source)
>        at com.thoughtworks.xstream.XStream.marshal(Unknown Source)
>        at com.thoughtworks.xstream.XStream.toXML(Unknown Source)
>
>To be clear, Xstream is not hot redeployed but the Objects to serialize are.
>Restarting Jboss solves the issue but this is quite annoying.
>
>We're using SUN JDK 1.4.2
>
>Thanks,
>
>Stéphane
>



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira