You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@river.apache.org by "Ron Mann (JIRA)" <ji...@apache.org> on 2007/07/27 21:02:54 UTC

[jira] Created: (RIVER-124) Semantics for serializing entry fields is probably not what we want

Semantics for serializing entry fields is probably not what we want
-------------------------------------------------------------------

                 Key: RIVER-124
                 URL: https://issues.apache.org/jira/browse/RIVER-124
             Project: River
          Issue Type: Improvement
          Components: net_jini_core
    Affects Versions: jtsk_2.1
            Reporter: Ron Mann
            Priority: Minor


Bugtraq ID [6278784|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6278784]
The entry spec states "The serialized form for each field is a
java.rmi.MarshalledObject object instances.", while this was ok
(though perhaps a tad narrow) in the per-2.0 universe, it is more
problematic in the post-2.0 universe where we want to allow for
(require?) net.jini.io marshaling, not just java.rmi style
marshaling - the primary operative difference being stub replacement.


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