I've been trying to figure out why some of the tests fail in JBoss5
but work in JBoss4.2, even though the code and config looks the same.
No matter how hard I looked at the code I couldn't see the difference. :-)
The answer is actually that JBoss5 spots the error during deployment
while 4.2 doesn't.
e.g. I couldn't figure out why this config was working in JBoss-4.2 but not in JBoss5
<server> <mbean code="org.jboss.test.cts.service.CtsCmpService" name="jboss.test:service=CtsCmpServiceV1"> <attribute name="HomeJndiName">v1/local/CtsCmp2Bean</attribute> <depends>jboss.j2ee:service=EJB,jndiName=v1/CtsCmp2Bean</depends> </mbean> </server>
Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.test:service=CtsCmpServiceV1 State: CONFIGURED I Depend On: jboss.j2ee:service=EJB,jndiName=v1/CtsCmp2Bean --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.j2ee:service=EJB,jndiName=v1/CtsCmp2Bean State: NOTYETINSTALLED Depends On Me: jboss.test:service=CtsCmpServiceV1 org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1385)
Things like the order of/missing elements in the DD etc are now better detected by the metadata layer in JBoss5. :)