You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "John McClain (JIRA)" <ji...@apache.org> on 2007/07/27 21:58:53 UTC
[jira] Created: (RIVER-129) EN spec should emphasize importance of
consistent serial forms
EN spec should emphasize importance of consistent serial forms
--------------------------------------------------------------
Key: RIVER-129
URL: https://issues.apache.org/jira/browse/RIVER-129
Project: River
Issue Type: Bug
Affects Versions: jtsk_1.1
Reporter: John McClain
Priority: Minor
Bugtraq ID [4696449|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4696449]
EN.1.5 states that {{MarshalledObject.equals}} is used for match operations, but does not make explicit that the declared types of fields, and the actual types of objects stored in those fields (including any objects nested within them) must be designed to produce consistent serial forms to make match operations reliable. Consistent serial forms means that a given instance always serializes the same, and a given instance that is serialized, deserialized, and then reserialized produces the same form as the initial serialization. A particular example where this has broken down is in the Service UI spec, where a field is declared to be of type {{java.util.Set}}, but existing {{Set}} implementations are not specified to (and in fact are not implemented to) produce consistent serial forms. Anyone designing an entry class needs to think hard about what fields might be used for matching, and worry about consistent serial forms.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-129) EN spec should emphasize importance of
consistent serial forms
Posted by "John McClain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John McClain updated RIVER-129:
-------------------------------
Component/s: net_jini_core
> EN spec should emphasize importance of consistent serial forms
> --------------------------------------------------------------
>
> Key: RIVER-129
> URL: https://issues.apache.org/jira/browse/RIVER-129
> Project: River
> Issue Type: Bug
> Components: net_jini_core
> Affects Versions: jtsk_1.1
> Reporter: John McClain
> Priority: Minor
>
> Bugtraq ID [4696449|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4696449]
> EN.1.5 states that {{MarshalledObject.equals}} is used for match operations, but does not make explicit that the declared types of fields, and the actual types of objects stored in those fields (including any objects nested within them) must be designed to produce consistent serial forms to make match operations reliable. Consistent serial forms means that a given instance always serializes the same, and a given instance that is serialized, deserialized, and then reserialized produces the same form as the initial serialization. A particular example where this has broken down is in the Service UI spec, where a field is declared to be of type {{java.util.Set}}, but existing {{Set}} implementations are not specified to (and in fact are not implemented to) produce consistent serial forms. Anyone designing an entry class needs to think hard about what fields might be used for matching, and worry about consistent serial forms.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.