river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Hurley (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-70) Outrigger does not store lookup locators in marshalled form
Date Thu, 26 Jul 2007 18:31:04 GMT
Outrigger does not store lookup locators in marshalled form
-----------------------------------------------------------

                 Key: RIVER-70
                 URL: https://issues.apache.org/jira/browse/RIVER-70
             Project: River
          Issue Type: Bug
          Components: com_sun_jini_outrigger
    Affects Versions: jtsk_1.1
            Reporter: Jim Hurley
            Priority: Minor


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

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