river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John McClain (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-130) JavaSpaces spec is silent on schema evolution
Date Fri, 27 Jul 2007 20:02:53 GMT
JavaSpaces spec is silent on schema evolution

                 Key: RIVER-130
                 URL: https://issues.apache.org/jira/browse/RIVER-130
             Project: River
          Issue Type: Improvement
          Components: net_jini_space
    Affects Versions: jtsk_1.0
            Reporter: John McClain

Bugtraq ID [4256312|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4256312]

User write entries of class {{Foo}}, modifies the class {{Foo}} (adding fields say) and then
write more entries....should anything reasonable happen?  At the very least we should put
verbiage in the spec saying that the results are undefined.


We might also want to consider throwing an exception so that client program is notified of
this condition

An intresing example of this problem in real life was the removal of the static
serVerID from Serializable between 1.2 and 1.2.2.  This caused problems because
this made Entries from 1.2 VM have a different number of field as those from 1.2.2 VMs

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message