The first issue is documented as Bug#516649. Note that if I package the sar and ejb-jar in an ear, deployment on startup works. I don't have a problem with requiring this type of packaging if it simplies the deployment logic and eliminates the number of locations where depends tags need to be handled.
Yes, I would say that the invoke and invokeHome ops should thrown an exception if they are used if the container is not in the started state. ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, February 12, 2002 2:19 PM Subject: Re: [JBoss-dev] Mbean dependancies > I'll take a look at these. > > I think the first will require adding a depends element to jboss.xml which > will translate into a dependency of the application on the referenced > mbean. This will also require making Application into an mbean, which I > want to do anyway. > > btw my change for allowing things to depend on ejbs puts the ejb container > mbean in the mbean server when it is created, not after it is started. > Should I make it so invoke and invokeHome throw exceptions if the Container > is not started? > > david jencks > > On 2002.02.12 15:48:09 -0500 Scott M Stark wrote: > > Two things I am seeing that I would appreciate you considering when > > you in there looking at the deployment stuff are the following: > > > > 1. An mbean in a sar that uses EJBs included in the sar as an ejb jar > > with the following depends statement: > > <server> > > <mbean code="org.jboss.test.perf.test.PerfTest" > > name="jboss.test:service=PerfTest"> > > <!-- We need the DefaultDS DataSource connection for entity beans --> > > <depends>jboss:service=ConnectionFactoryLoader,name=DefaultDS</depends> > > </mbean> > > </server> > > > > fails on startup of the server because the entity beans are deployed > > before > > the > > DefaultDS is available. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
