river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Firmstone (JIRA)" <j...@apache.org>
Subject [jira] Updated: (RIVER-316) RFC Library, Application & Class Versioning, Dynamically Mobile Codebases and Classloading enhancements
Date Fri, 24 Jul 2009 13:16:14 GMT

     [ https://issues.apache.org/jira/browse/RIVER-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Peter Firmstone updated RIVER-316:
----------------------------------

    Summary: RFC Library, Application & Class Versioning, Dynamically Mobile Codebases
and Classloading enhancements  (was: RFC codebase versioning and Classloading enhancements
for PreferredClassProvider)

> RFC Library, Application & Class Versioning, Dynamically Mobile Codebases and Classloading
enhancements
> -------------------------------------------------------------------------------------------------------
>
>                 Key: RIVER-316
>                 URL: https://issues.apache.org/jira/browse/RIVER-316
>             Project: River
>          Issue Type: New Feature
>          Components: net_jini_loader
>         Environment: All
>            Reporter: Peter Firmstone
>         Attachments: Java Classloader issues relating to Jini smli_tr-2006-149.pdf
>
>
> Request for Comments:
> Proposal to add support for http Codebase class versioning, to enable River User devolopers,
to provide distinction between classes with the same fully qualified class name when code
differences created by refactoring packages or library updates break backward compatibility
between classes contained within that library or package.
> A dependency tree array object (contains dependency references between classes, fully
qualified class names are stored as String objects) returned by the new ClassDepend tool (replacement
of classdep functionality) may be suitable (with some modification) for recording class versioning,
for later navigation of the codebase for class version verification, perhaps this could be
stored in serialized form with the codebase.
> The ASM library might be used to modify existing, externally sourced library class file
bytecodes to add a classVersionID immutable field, with an accessor method, for library code
used in codebases, to mark the class files with the library release version.
> serialVersionUID (when it exists), along with the classVersionID, might be used to determine
the dependency and backward compatibility of classes in a codebase, this information could
be stored in the dependency tree along with the classVersionID and fully qualified class name.

-- 
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