[RIVER-154] Entry spec should distinguish between entry serialization vs field serialization

• Type: Improvement
• Status: Open
• Priority: Trivial
• Resolution: Unresolved
• Affects Version/s: jtsk_1.0
• Component/s: net_jini_core
• Bugtraq ID: 4230054
• Assignee: Unassigned
• Reporter: Robert Scheifler
• Created: 30/Jul/07 19:27
• Updated: 30/Jul/07 19:27

Description

Bugtraq 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".