[ http://issues.apache.org/jira/browse/GERONIMO-1980?page=comments#action_12418228 ]
Aaron Mulder commented on GERONIMO-1980: ---------------------------------------- The plugin installer does not use any long-lived threads. They're only used for the duration of a single install command. I mean, it's longer than a web request, but normally under a minute. (And the web handler threads are really log-lived I suspect.) > Move Plugin Installer from rmi-naming to j2ee-system > ---------------------------------------------------- > > Key: GERONIMO-1980 > URL: http://issues.apache.org/jira/browse/GERONIMO-1980 > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
