harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stepan Mishura (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-91) Serialization: fails to deserialize stream in case of added class to hierarchy
Date Tue, 14 Feb 2006 15:52:40 GMT
Serialization: fails to deserialize stream in case of added class to hierarchy

         Key: HARMONY-91
         URL: http://issues.apache.org/jira/browse/HARMONY-91
     Project: Harmony
        Type: Bug
  Components: Classlib  
    Reporter: Stepan Mishura
    Priority: Minor

According to the serialization spec. adding classes is compatible change and shouldn't affect
serialization. The current implementation of java.io.ObjectInputStream class fails to deserialize
stream (reconstitute an object) in this case. Particularly, it fails when super class for
added class contains serialized fields.

The following tests from security2 fail because of this bug:
1) javax/security/auth/login/serialization/SerAccountExpiredExceptionTest.java (added javax.security.auth.login.AccountException
in Java Spec 5.0 as super class)   
2) javax/security/auth/login/serialization/SerCredentialExpiredExceptionTest.java (added javax.security.auth.login.CredentialException
in Java Spec 5.0 as super class)   

I've create serial form by hands to provide minimized test case with dynamic generation of
required serialization byte array (i.e. serialization form now is immune for test class rename)
but it is still quite long. So I'll add a test case to reproduce the failure as a patch for
this JIRA bug.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message