Actually I misread your question, but I think the
answer is similar. I think you need to declare a dependency on the Service or
Services that connect those datasources and bind them into JNDI. I'm not
sure exactly which ones.
-----Original Message-----
From: Steven Harris [mailto:[EMAIL PROTECTED]
Sent: Friday, August 22, 2003 10:27 AM
To: '[EMAIL PROTECTED]'
Subject: [JBoss-user] RE: [JBoss-user] Sar deployment order questionYou can make your application an MBean in an ear with your jar and sar included in that ear.In your jboss-service.xml <mbean> def, you can put <depends>jboss:service=Naming</depends> to declare that starting your application depends on JNDI naming service being started. In the examples for JBoss Admin & Development, look at the examples for chapter 2.-----Original Message-----
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2003 11:32 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Sar deployment order questionFirst of all, I will put those JAR and WAR into an EAR file, not a SAR.
Then apart from that, sorry I don't know the answer :/
On Thu, 2003-08-21 at 11:52, Davide Pozza wrote:Hi all I've packager my application's jar and war into a sar archive and at the first startup of jboss I receive many deployment errors. I know that this is because the datasources used by my application are deployed and bounded to jndi after the sar deployment, but I don't know hot to tell jboss that my application has to be deployed at the end of the startup process. Any suggestions? Thanks Davide