[RIVER-67] Mahalo does not store lookup locators in marshalled form

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: jtsk_2.1
• Component/s: com_sun_jini_mahalo
• Bugtraq ID: 4941110
• Assignee: Unassigned
• Reporter: Robert Resendes
• Created: 26/Jul/07 16:27
• Updated: 10/Aug/07 21:28

Description

Bugtraq ID 4941110

Mahalo stores its lookup locators in serialized rather than marshalled form,
meaning that any codebases associated with the locators will be lost. If a
lookup locator with a remote codebase were specified as an initial locator, or
via the administrative interface, Mahalo would be unable to restart if the class
definition for the locator were not available in Mahalo's class path. Note that,
in current practice, we don't expect lookup locators to be implemented by
downloaded code, mostly because Mahalo does not call the getRegistrar method that
would be the most likely candidate for customization in a subclass, so the
impact of this problem is probably small.Mahalo stores its lookup locators in serialized rather than marshalled form,
meaning that any codebases associated with the locators will be lost. If a
lookup locator with a remote codebase were specified as an initial locator, or
via the administrative interface, Mahalo would be unable to restart if the class
definition for the locator were not available in Mahalo's class path. Note that,
in current practice, we don't expect lookup locators to be implemented by
downloaded code, mostly because Mahalo does not call the getRegistrar method that
would be the most likely candidate for customization in a subclass, so the
impact of this problem is probably small.

Issue Links

• is related to: RIVER-133 Norm does not store lookup locators in marshalled form