java.io.NotSerializableException: org.exolab.castor.xml.FileLocation

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 0.9.3.9
  • Fix Version/s: None
  • Component/s: XML
  • Labels:
    None
  • Environment:
    Operating System: Linux
    Platform:
  • Bugzilla Id:
    930

Description

When using Castor in conjunction with JBoss I am passing Castor generated java
objects (generated via the SourceGenerator, and populated via the unmarshal
method) as return values to remote session bean calls. This requires the
object to be Serializeable. The source Castor generated implements
Serializeable but the NotSerializeable exception is throw at runtime. This
does not happen 100% of the time.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Keith Visco added a comment -

Can you provide more information, such as the schema that is being used to
generate the source, are you using version 0.9.3.9 or the current CVS version?
Since it doesn't happen all the time...under what constraints does it happen.
For example...how can we reproduce it?

Show
Keith Visco added a comment - Can you provide more information, such as the schema that is being used to generate the source, are you using version 0.9.3.9 or the current CVS version? Since it doesn't happen all the time...under what constraints does it happen. For example...how can we reproduce it?
Hide
Permalink
amccullo added a comment -

I am using version 0.9.3.9. The circumstances that caused this are unknown to
me, it happened 2 times in a row and not since. I am running inside JBoss so I
simply restarted the application server and the problem went away. I will
attempt to attach a subset of the xsd but I am not sure what I will be able to
include due to business restrictions. I do not have a test case that will
reproduce this... I will look at the source this evening to see if I can
pinpoint the issue.

Show
amccullo added a comment - I am using version 0.9.3.9. The circumstances that caused this are unknown to me, it happened 2 times in a row and not since. I am running inside JBoss so I simply restarted the application server and the problem went away. I will attempt to attach a subset of the xsd but I am not sure what I will be able to include due to business restrictions. I do not have a test case that will reproduce this... I will look at the source this evening to see if I can pinpoint the issue.
Hide
Permalink
amccullo added a comment -

I was not successfull in searching the code for the cause but I have narrowed
it down somewhat. I have validation (both SAX and Castor) turned off in the
castor.properties file. The xml that was passed to the static unmarshal method
in the generated source was not valid. This seems to happen repeatably under
these conditions, with any generated object.

0. Set validation to OFF
1. Generate source from xsd
2. Generate invalid xml for xsd
3. Unmarshal invalid xml
4. Serialize object

Show
amccullo added a comment - I was not successfull in searching the code for the cause but I have narrowed it down somewhat. I have validation (both SAX and Castor) turned off in the castor.properties file. The xml that was passed to the static unmarshal method in the generated source was not valid. This seems to happen repeatably under these conditions, with any generated object. 0. Set validation to OFF 1. Generate source from xsd 2. Generate invalid xml for xsd 3. Unmarshal invalid xml 4. Serialize object
Hide
Permalink
Keith Visco added a comment -

Are you trying to serialze exceptions? FileLocation is a class that is only used
inside Castor exceptions.

Show
Keith Visco added a comment - Are you trying to serialze exceptions? FileLocation is a class that is only used inside Castor exceptions.
Hide
Permalink
amccullo added a comment -

No I am actually just serializing the Castor generated object with validation
set to false in the castor.properties file. Does castor validate anyway and
just catch the exception internally? It seems as if the exception is being
stored in the object in this case (but I could be way off).

Show
amccullo added a comment - No I am actually just serializing the Castor generated object with validation set to false in the castor.properties file. Does castor validate anyway and just catch the exception internally? It seems as if the exception is being stored in the object in this case (but I could be way off).
Hide
Permalink
Keith Visco added a comment -

Marking as LATER until we have a test case which can demonstrate the problem. I
won't close this issue out as it may be a valid problem, but until we can see
the problem there is nothing we can actually do to fix it.

Show
Keith Visco added a comment - Marking as LATER until we have a test case which can demonstrate the problem. I won't close this issue out as it may be a valid problem, but until we can see the problem there is nothing we can actually do to fix it.

People

  • Assignee:
    Keith Visco
    Reporter:
    amccullo
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: