river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Resendes (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-66) Mercury does not store lookup locators in marshalled form
Date Thu, 26 Jul 2007 16:28:03 GMT
Mercury does not store lookup locators in marshalled form
---------------------------------------------------------

                 Key: RIVER-66
                 URL: https://issues.apache.org/jira/browse/RIVER-66
             Project: River
          Issue Type: Improvement
          Components: com_sun_jini_mercury
    Affects Versions: jtsk_2.1
            Reporter: Robert Resendes
            Priority: Minor


Bugtraq ID [4941108|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4941108]

Mercury 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, Mercury would be unable to restart if the class
definition for the locator were not available in Mercury's class path.  Note that,
in current practice, we don't expect lookup locators to be implemented by
downloaded code, mostly because Mercury 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.Mercury 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, Mercury would be unable to restart if the class
definition for the locator were not available in Mercury's class path.  Note that,
in current practice, we don't expect lookup locators to be implemented by
downloaded code, mostly because Mercury 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.

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


Mime
View raw message