We have developed an Application with the structure described below
test.ear
| test.jar
| test.war
| startup.sar
| META-INF
| jboss-service.xml
| META-INF
| jboss-app.xml
| application.xml
In order to ensure that the MBean Services in the startup.sar gets
started after the deployment of all the EJBs in test.jar, I had used the
depends tag in the jboss-service.xml in the startup.sar as given below
<?xml version="1.0" encoding="UTF-8"?>
|
| <server>
|
| <mbean code="test.Production" name="test.com:service=Production">
| <depends>jboss.j2ee:service=EjbModule,module=test.jar</depends>
| </mbean>
|
| </server>
The configuration worked properly in jboss version 3.2.3. The Service
MBeans were invoked after the deployment of the EJBs in test.jar.
After migrating to JBoss 4.0.2, I could see that the dependency check
is not enforced. (i.e) The Beans in the startup.sar get executed even before
the EJBs are deployed.
Any help would be appreciated.
Thanks,
Krish.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881957#3881957
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881957
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
