You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Prasad Kashyap (JIRA)" <ji...@apache.org> on 2007/07/25 17:56:31 UTC

[jira] Updated: (GERONIMO-1980) Move Plugin Installer from rmi-naming to j2ee-system

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

Prasad Kashyap updated GERONIMO-1980:
-------------------------------------

    Fix Version/s:     (was: 2.0-M5)
                       (was: 1.x)
                   2.0.x

> Move Plugin Installer from rmi-naming to j2ee-system
> ----------------------------------------------------
>
>                 Key: GERONIMO-1980
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-1980
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: buildsystem, Plugins
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>             Fix For: 2.0.x
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.