You can either put the ejb jar in the sar or put both in an ear. Use jboss 3 from cvs or you may have class visibility problems.
If you put the jar in the sar it will be deployed first. If you put both in an ear the sar will be deployed first. If you need even more control over timing and need the mbeans to wait to be started (assuming they participate in jboss service lifecycle management) until the ejbs are started, use depends elements to the mbeans representing the ejb containers or the mbean representing the ejb module (NOT the jsr-77 mbeans for these). However, I can't think why just packing one way or the other wouldn't work fine. david jencks On 2002.03.01 18:41:50 -0500 Eric Jain wrote: > I'd like to merge a .sar file (containing a scheduled class and a > jboss-service.xml) with a .jar file (containing ejbs), so that the > scheduled > classes can access the beans through their local interfaces. I believe > this > is possible with JBoss 3.0, but am not sure about the file layout and > naming > required to get this to work? > > > -- > Eric Jain > > > _______________________________________________ > 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
