[jira] Commented: (GERONIMO-2017) MEJB should not extend Management because it extends EJBObject pulling in requirements for the ejb-spec

["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