I have an ear with a few ejb-jar's in it, plus a war.  The war needs 
each of the ejb-jars, but no ejb-jars need eachother (they can be 
dropped into deploy by themselves no problem) EXCEPT one.  There is one 
"control" ejb-jar that HAS to be the last ejb-jar to be deployed from 
the ear, since it uses the other ejb-jars.

I have the "control" ejb-jar listed after the ones it depends on in my 
ear's application.xml file.

In JBoss-2.4.4_Tomcat-X.XX I have no problems deploying my ear, and the 
ejb-jars deploy in the proper order.

HOWEVER, in JBoss-3.0.0beta_Tomcat-4.0.2, the "control" ejb-jar gets 
deployed before some of the other ejb-jars it depends on get deployed, 
and I get a bunch of exceptions when my application inits (since it 
can't find the "control" stuff).

"... Serious error in init:
... org.jboss.deployment.DeploymentException: Bean XXX not found within 
this application.
        at org.jboss.ejb.Container.setupEnvironment(Container.java: 906)..."

Did JBoss 2.4.4 respect the order in application.xml, or did it have a 
smart way of resolving dependencies before initialization?  Did 
something change in this regard in 3.0.0beta?

Thanks muchly,
David


_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to