You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Brian Murphy (JIRA)" <ji...@apache.org> on 2007/08/04 19:09:54 UTC

[jira] Created: (RIVER-190) Fiddler stores local attributes in marshalled form, prevents codebase evolution

Fiddler stores local attributes in marshalled form, prevents codebase evolution
-------------------------------------------------------------------------------

                 Key: RIVER-190
                 URL: https://issues.apache.org/jira/browse/RIVER-190
             Project: River
          Issue Type: Bug
          Components: com_sun_jini_fiddler
    Affects Versions: jtsk_2.0_001
            Reporter: Brian Murphy
            Priority: Minor


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

Related Bugs	 4959703 , 4959705 , 4959692 , 4959687
Submit Date	25-NOV-2003
Description	
   Fiddler 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 attribute 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.Fiddler stores all of its attributes in marshalled form in its  customer 
   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 attribute 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.
Posted Date : 2006-03-06 13:46:03.0
Work Around	
Rename the download codebase whenever its contents are changed, 
and continue to supply the original codebase.

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