I wrote and deployed an MDB under JBoss3. Everytime I launch JBoss, initialization of this MDB fails because of dependent resources not yet initialized. In particular, I get:
javax.management.InstanceNotFoundException: jboss.jca:service=CachedConnectionManager is not registered.
javax.naming.NameNotFoundException: DefaultJMSProvider not bound
If then I re-deploy the MDB, everything is OK (since the dependent resources are available at this point).
Question: I specified resource-refs and JMS destination in the ejb-jar.xml and jboss.xml files, AND created a separately deployed jbossmq-blah-service.xml file for defining the MDB inbound queue. I know these deployment setup are correct because deployment of my MDB AFTER JBoss has started works. What else have I missed that causes the JBoss launch to fail?
Question: Is there anything similar to the tag for MBean deployment that I can use in deploying EJBs to specify initialization dependency? I want to force JBoss to initialize certain MBeans before it initializes my EJB.
Thx in advance for your help.