wait for the new deployer, make a mdb jar that contains the ejb jar, the ejb jar will always be deployed before the containing one.
This is dependency by containment. Other than that we need an explicit language for dependencies and it should have an explicit "depends" language like we do the mbean. While the above solution will work the one with an explicit language needs to be implemented. marcf |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Scotney, |Derek |Sent: Wednesday, January 16, 2002 5:54 AM |To: [EMAIL PROTECTED] |Subject: [JBoss-user] Deployment dependancy problem | | |Hi All | |If anyone can help me with the following problem I would really appreciate |it. The problem is as follows: | |I have a few beans that are being deployed when JBoss is started. One is an |entity bean and the other is a Message Driven Bean. The MDB needs |to use the |entity bean in it's onMessage() method. This is no problem when |there is no |messages in the JMS queue at startup. When there are messages in the queue |at startup, the MDB starts processing them before the entity bean is fully |deployed and I get a NamingException when I do a lookup for the bean. | |Is there any way to make a bean dependant on another bean or specify a |specific deployment sequence? | |Any help\suggestions would be appreciated. | |Thanks, | |Derek. | |_______________________________________________ |JBoss-user mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
