james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danny Angus" <da...@apache.org>
Subject RE: Download jars instead of keeping in CVS?
Date Tue, 04 Feb 2003 10:21:45 GMT
> Danny, it seems that you have a good idea of what you would like to see, 
> could you give me some pointers, maybe an implementation idea? :-)

I don't think that I'm concerned with the repository *using* version information contained
in the jars, if it keeps track externally and can return a file for a requiest containing
name and version. The client should be able to tell whether or not a correctly named jar does
or does not contain the intended library version. And furthermore that it can continue to
tell even if the filename changes.

Of course this is what the manifest is supposed to do.

What we need is a library management tool to allow shared libraries to be installed and maintained
centrally by the JVM, this can be queried by application classloaders to discover the file
containing the required version of the relevant package, the returned path would be added
to the classloader.

Then library installation would be a case of defining dependancies and pointing this tool
at a URL containing jars for download.
If the version is found on the system no action is necessary,
Download the jar 
Confirm that the downloaded jar is indeed the expected version, 
Store it on the filesystem 
Provide classloaders with the path when they request the package version.

Of course there are two immediate concerns, 

1/ there is a requirement for strong names, whereby package names cannot collide.
2/ there is a security issue involved in allowing applications to access any installed library,
even those not explicitly required by the application.


To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org

View raw message