geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bohn (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-1848) Shared Library support via a GBean
Date Sat, 15 Apr 2006 14:08:01 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1848?page=all ]

Joe Bohn updated GERONIMO-1848:
-------------------------------

    Attachment: 1848_sharedlib.patch

patch created on windows xp .  Apply patch from geronimo root.

One question I had was if  the attribute values had to be specified in both the configuration
plan in order for them to be in the server config.xml.  If not, then perhaps we should remove
the values from the plan.xml in the config so that they could be omitted from the config.xml
if we desired to set the value to null.

> Shared Library support via a GBean
> ----------------------------------
>
>          Key: GERONIMO-1848
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1848
>      Project: Geronimo
>         Type: New Feature
>     Security: public(Regular issues) 
>   Components: deployment
>     Versions: 1.1
>  Environment: all
>     Reporter: Joe Bohn
>     Assignee: Joe Bohn
>      Fix For: 1.1
>  Attachments: 1848_sharedlib.patch
>
> Expose the functionality that Dain introduced for shared libraries extending the MultiParentClassLoader.
 
> This particular change introduces a GBean (sharedlib) that accepts parameters to extend
the multiparent class loader with the location of jars or classes.   The GBean calls out rmi-naming
as a parent dependency to pull in as few extraneous classes as possible.   
> An application would exploit this function by creating a parent dependency on the sharedlib
GBean and add the common jars/classes to the shared directories (by default var/shared/lib
and var/shared/classes).  The config.xml can be updated to point to different or additional
locations for shared content.

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