geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1980) Move Plugin Installer from rmi-naming to j2ee-system
Date Sat, 24 Jun 2006 11:25:30 GMT
    [ ] 

Aaron Mulder commented on GERONIMO-1980:

Yes, that sounds like a good idea to pursue.  The only question is where to put the DefaultThreadPool
that the plugin installer depends on.  Are you OK putting that in the j2ee-system?  

> Move Plugin Installer from rmi-naming to j2ee-system
> ----------------------------------------------------
>          Key: GERONIMO-1980
>          URL:
>      Project: Geronimo
>         Type: Improvement
>     Security: public(Regular issues) 
>   Components: buildsystem, Plugins
>     Versions: 1.1
>     Reporter: Aaron Mulder
>      Fix For: 1.2

> Ideally, the plugin installer will be as high in the food chain as possible, so it can
replace as much as possible without shutting itself down.  Currently it is in rmi-naming.
> I tried moving it to j2ee-system, which requires the following new dependencies for j2ee-system:
>  - geronimo-core
>  - geronimo-management
>  - geronimo-util
>  - geronimo-j2ee-management_1.0_spec
>  - concurrent
> Somehow, the net result of this was that the OpenEJB config could not load javax.ejb.EJBObject,
so there's something funky going on with the class loaders when the above changes are made.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message