MDB (possibly EJB) with <depends> can cause NPE upon create

SourceForge Submitter: genman .

Log statements:

2004-07-27 21:23:55,875 INFO [EARDeployer] Undeploying
J2EE application, destroy step:
file:/home/eross/src/servers/jboss-3.2.6/server/default/deploy/xxx.ear
2004-07-27 21:23:55,946 INFO [EARDeployer] Init J2EE
application:
file:/home/eross/src/servers/jboss-3.2.6/server/default/deploy/xxx.ear
2004-07-27 21:23:56,090 ERROR [MessageDrivenContainer]
Initialization failed
jboss.j2ee:jndiName=local/MDB,service=EJB
java.lang.NullPointerException
at
org.jboss.ejb.Container.createService(Container.java:571)
at
org.jboss.ejb.MessageDrivenContainer.createService(MessageDrivenContainer.java:155)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:219)
at
....

Reproduction steps:

Create an .ear with a MDB which has a <depends> on a
MBean in another .ear or .sar file. Redeploy the
MBean-containing .ear. Example jboss.xml:

<jboss>
<enterprise-beans>

<message-driven>
<ejb-name>MyMDB</ejb-name>
<destination-jndi-name>queue/mymdb</destination-jndi-name>
<depends>example:service=MyService</depends>
</message-driven>
</enterprise-beans>
</jboss>

Suggestion:

In
src/main/org/jboss/ejb/Container.java

line 625: do not NULL this.classLoader;

Possibly other members should not be nulled. I'm
wondering why the extensive null-ing is even necessary.