[ 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
