You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Joe Bohn (JIRA)" <de...@geronimo.apache.org> on 2006/05/12 22:56:08 UTC
[jira] Created: (GERONIMO-2017) MEJB should not extend Management
because it extends EJBObject pulling in requirements for the ejb-spec
MEJB should not extend Management because it extends EJBObject pulling in requirements for the ejb-spec
-------------------------------------------------------------------------------------------------------
Key: GERONIMO-2017
URL: http://issues.apache.org/jira/browse/GERONIMO-2017
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Components: management
Versions: 1.1
Environment: all
Reporter: Joe Bohn
Assigned to: David Jencks
Fix For: 1.1
Attempting to remove the open-ejb spec dependency from the config\rmi-naming I received a ClassDefNotFound error on EJBObject.
David Jencks dug into this and figured the problem was due to the fact that MEJB had a requirement on EJBObject because it was implementing the Management interface which extends EJBObject. IIUC this was making it a requirement that we include the EJBObject class from the ejb spec in j2ee-server. There is no need for MEJB to implement management since anyone using it as a gbean isn't likely to have ejbs available.
--
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
[jira] Commented: (GERONIMO-2017) MEJB should not extend Management
because it extends EJBObject pulling in requirements for the ejb-spec
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2017?page=comments#action_12383311 ]
David Jencks commented on GERONIMO-2017:
----------------------------------------
This is all true but unfortunately rmi-naming has to include the j2ee management and ejb specs anyway since the thread pool requires (theoretically anyway) the Stats class from management.
> MEJB should not extend Management because it extends EJBObject pulling in requirements for the ejb-spec
> -------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2017
> URL: http://issues.apache.org/jira/browse/GERONIMO-2017
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: management
> Versions: 1.1
> Environment: all
> Reporter: Joe Bohn
> Assignee: David Jencks
> Fix For: 1.1
>
> Attempting to remove the open-ejb spec dependency from the config\rmi-naming I received a ClassDefNotFound error on EJBObject.
> David Jencks dug into this and figured the problem was due to the fact that MEJB had a requirement on EJBObject because it was implementing the Management interface which extends EJBObject. IIUC this was making it a requirement that we include the EJBObject class from the ejb spec in j2ee-server. There is no need for MEJB to implement management since anyone using it as a gbean isn't likely to have ejbs available.
--
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
[jira] Commented: (GERONIMO-2017) MEJB should not extend Management
because it extends EJBObject pulling in requirements for the ejb-spec
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2017?page=comments#action_12383345 ]
Aaron Mulder commented on GERONIMO-2017:
----------------------------------------
It's not just theoretical -- there's a page in the console that shows all the activity for a thread pool using the stats provided by the thread pool. The reason there's a thread pool is in the plugin installer uses it. I'd actually like to move the thread pool and plugin installer up to the system module, but that didn't work either.
The core, system, and mangement modules have become pretty interdependent. It would be nice to strategically reconsider what goes where, and lay out the expectations for what can go into each level of the server assembly.
> MEJB should not extend Management because it extends EJBObject pulling in requirements for the ejb-spec
> -------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2017
> URL: http://issues.apache.org/jira/browse/GERONIMO-2017
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: management
> Versions: 1.1
> Environment: all
> Reporter: Joe Bohn
> Assignee: David Jencks
> Fix For: 1.1
>
> Attempting to remove the open-ejb spec dependency from the config\rmi-naming I received a ClassDefNotFound error on EJBObject.
> David Jencks dug into this and figured the problem was due to the fact that MEJB had a requirement on EJBObject because it was implementing the Management interface which extends EJBObject. IIUC this was making it a requirement that we include the EJBObject class from the ejb spec in j2ee-server. There is no need for MEJB to implement management since anyone using it as a gbean isn't likely to have ejbs available.
--
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
[jira] Closed: (GERONIMO-2017) MEJB should not extend Management
because it extends EJBObject pulling in requirements for the ejb-spec
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2017?page=all ]
David Jencks closed GERONIMO-2017:
----------------------------------
Resolution: Won't Fix
after trying a lot of things I don't think we can make any dependency changes related to this without moving gbeans around, in particular moving the thread pool out of rmi-naming. I'm not sure that move would be a good idea.
> MEJB should not extend Management because it extends EJBObject pulling in requirements for the ejb-spec
> -------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2017
> URL: http://issues.apache.org/jira/browse/GERONIMO-2017
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: management
> Versions: 1.1
> Environment: all
> Reporter: Joe Bohn
> Assignee: David Jencks
> Fix For: 1.1
>
> Attempting to remove the open-ejb spec dependency from the config\rmi-naming I received a ClassDefNotFound error on EJBObject.
> David Jencks dug into this and figured the problem was due to the fact that MEJB had a requirement on EJBObject because it was implementing the Management interface which extends EJBObject. IIUC this was making it a requirement that we include the EJBObject class from the ejb spec in j2ee-server. There is no need for MEJB to implement management since anyone using it as a gbean isn't likely to have ejbs available.
--
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