I think until marc shows us what he has been up to you will either have to deploy 2 packages by hand in the right order or deploy 2 packages and include a depends tag in the mbean config referring to the Container mbean for the entity. With luck, this will force the service mbean to wait until the entity is deployed. I don't know if the Container is actually participating fully in the dependency management scheme.
You might also try putting everything in an ear, embedding both the jar and sar. There is some code to deploy sar in ears but I don't know if it works. You will probably also have to use the depends trick since I believe sars should be deployed first by default. david jencks On 2002.01.14 03:58:28 -0500 Sacha Labourey wrote: > Hello, > > For the HttpSession clustering stuff, I need, by dragging a single .sar > in > deploy, to: > - deploy an entity bean > - deploy and start a JMX service that will use the entity bean > > (yes, there is a dependency between the entity and the service) > > I've tried to make a standard SAR and, in it, added the bean JAR but > without > any success ( I think it is what Marc's code that he will commit should > do: > recursively deploy all jars. But in which order?) > > If the "implicit" method doesn't work (just putting everything in a SAR), > is > there an explicit method that is working? (putting the bean deployement > "command" directly in the services.xml file of the SAR) > > Thank you. Cheers, > > > > Sacha > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
