You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Bob Scheifler (JIRA)" <ji...@apache.org> on 2007/07/30 21:28:54 UTC
[jira] Created: (RIVER-154) Entry spec should distinguish between
entry serialization vs field serialization
Entry spec should distinguish between entry serialization vs field serialization
--------------------------------------------------------------------------------
Key: RIVER-154
URL: https://issues.apache.org/jira/browse/RIVER-154
Project: River
Issue Type: Improvement
Components: net_jini_core
Affects Versions: jtsk_1.0
Reporter: Bob Scheifler
Priority: Trivial
Bugtraq ID [4230054|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4230054]
IMHO the spec is ambigous regarding the serialization of the entry class (vs its fields).
[Section 1.3 of the entry specification]
"In a store operation, the class of the entry type itself is also
written with a MarshalledObject, ensuring that it, too, may be downloaded
from a codebase."
This implies (to me) that the class is sent as a MarshalledObject, when in fact only the classname/codebase is sent in our implementations (e.g. outrigger).
This distinction makes a semantic difference when passing Remote objects, for instance. If you pass it as a MarshalledObject, then you'd expect to pass the associated "stub" file. In our implementations, the actual class gets passed and not the "stub".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.