[jira] Commented: (RIVER-80) Mercury stores local attributes in marshalled form, prevents codebase evolution

["Fred Oliver (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RIVER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515866 ] 

Fred Oliver commented on RIVER-80:
----------------------------------

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 supplied by the service's download codebase.

> Mercury stores local attributes in marshalled form, prevents codebase evolution
> -------------------------------------------------------------------------------
>
>                 Key: RIVER-80
>                 URL: https://issues.apache.org/jira/browse/RIVER-80
>             Project: River
>          Issue Type: Bug
>          Components: com_sun_jini_mercury
>    Affects Versions: jtsk_2.0
>            Reporter: Fred Oliver
>            Priority: Minor
>
> Bugtraq ID [4959705|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4959705]
> Mercury stores all of its attributes in marshalled form in its persistent log,
> including its initial attributes, whose code is supplied by its download
> 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 attributed 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.

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