[RIVER-150] Reggie codebase evolution problematic for persisted local objects

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: jtsk_2.0
• Component/s: com_sun_jini_reggie
• Bugtraq ID: 4960295
• Assignee: Unassigned
• Reporter: Robert Scheifler
• Created: 30/Jul/07 16:46
• Updated: 11/Jan/10 06:06

Description

Bugtraq ID 4960295

Reggie stores all of its attributes, registered service proxies, and lookup
locators in marshalled form (or an equivalent) in its persistent log. This
includes Reggie's own proxy, as well as any attributes and lookup locators
whose code is supplied by Reggie's own codebase. When a codebase uses HTTPMD
URLs, the codebase needs to be changed whenever the contents of the download
JAR file changes, either due to additions or modifications in a patch release,
or with the addition of attributes. Such a change alters the codebase of any
attributes, proxies, and lookup locators supplied by the download JAR file,
either causing the service to drop them if the new export codebase has the same
name, or else requiring giving the updated codebase a new name.

WorkAround

Rename the download codebase whenever its contents are changed and continue to
supply the original codebase.

SuggestedFix

Don't store the codebase for attributes and lookup locators supplied
by Reggie's own codebase. Also, don't store Reggie's own proxy (see 4939735).

Issue Links

• relates to: RIVER-328 OSGi Bundles for Versioning Control and Codebase Evolution