[ https://issues.apache.org/jira/browse/TUSCANY-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ant elder closed TUSCANY-1084. ------------------------------ Resolution: Fixed > Java Serialization: The Type definition is overwritten in the registry within > the same scope > -------------------------------------------------------------------------------------------- > > Key: TUSCANY-1084 > URL: https://issues.apache.org/jira/browse/TUSCANY-1084 > Project: Tuscany > Issue Type: Bug > Components: Java SDO Implementation > Affects Versions: Java-M2 > Environment: All > Reporter: Hasan Muhammad > Fix For: Java-SDO-Mx > > Attachments: JavaSerializeDeserializeTestCase.java > > > When a DataObject is serialized using the java serialization ( > ObjectOutputStream.writeObject) and deserialized back using > ObjectInputStream.readObject, the types of the two dataobjects do not match, > even though this all in the same scope ( global in this case ). > During deserialization, it seems that the type of the dataobject cannot be > found, and it is creating the type again and simply overwrites the previously > registered type. This results in the dataobjects getting different types and > the test case fails. > There is another issue here, which is that currently there seems to be no way > to provide a scope when using these java serialization methods. For instance, > when using XMLHelper, you can get a scope defined XMLHelper. But how do you > do this when you are using the java serialization methods ? If you want me to > open another Jira for this i will. > Hasan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]