geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-955) Provide separate client container distribution
Date Tue, 22 Nov 2005 19:59:42 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-955?page=comments#action_12358294 ] 

David Jencks commented on GERONIMO-955:
---------------------------------------

There's a bunch of support for parts of this already implemented.

Using includes for the client.jar rather than manifest classpath dependencies would eliminate
the need for lib, although it might cause problems with endorsed/extension dirs.

The assembly plugin has code that will install a configuration into a config store and put
all its dependencies into a repository.  This can be leveraged to create a suitably minimal
repository for the client.

Here are a couple additional not-yet implemented ideas:
The app client builder should be examined to see if the app client dependencies are specified
independently of the ear dependencies and that they are not all munged together.

It would be best if the "finished"  app client could be distributed as a single jar, at least
as an option.  We could try classworlds/uberjar, although my past experience with it is that
it is about 10X slower than a regular classloader.  Alternatively we might be able to include
a repo with unpacked artifacts inside the jar and write a classloader that used an "offset"
into the jar.

> Provide separate client container distribution
> ----------------------------------------------
>
>          Key: GERONIMO-955
>          URL: http://issues.apache.org/jira/browse/GERONIMO-955
>      Project: Geronimo
>         Type: Improvement
>   Components: application client
>     Versions: 1.0-M4
>     Reporter: Aaron Mulder
>      Fix For: 1.x

>
> It would be ideal if you could install a "client container only" which required less
than the full 50+ MB of a Geronimo server.
> This would of course be for situations where the client was running on a different machine
than the server, or where the user running the client app didn't have necessary file permissions
on the server installation directory (e.g. to write a client log file).
> Perhaps one of the assemblies/ modules could do this; the trick will be to not include
the JARs (in the repository, etc.) that aren't needed by the client container.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message