Deployment of JARs before SARs, a little help please

[murray_fortescue]

Hi

The application I am working on has an ear that contains a sar and an jar file containing the ejb definitions. The MBean in my sar uses one of the ejbs in the jar, hence I wish to deploy the ejb jar first.

I have had a look through various posts that have had questions reguarding this already and have followed the advice given in those.

I have named the jar file : 1_appname.jar
and the sar file : 2_appname.sar

I have then commented out the org.jboss.deployment.DeploymentSorter and am using the PrefixDeploymentSorter instead.

My understanding is that this should then pick up the 1_appname.jar and deploy it before deploying the 2_appname.sar. Is this the case? If it is it is not working for me ... should I be setting something else as well?

I am using jboss 3.2.3, is there any other setting I should be looking at.

Thanks very much in advance

Murray

[darranl]

http://www.jboss.org/wiki/Wiki.jsp?page=HowCanAnMBeanDependOnASessionBean

[murray_fortescue]

Hi darranl,

Thanks for the response. I have followed the suggestion in the FAQ so the mbean declaration in the service.xml class is

 <mbean code="com.Scheduler"
 name="jboss.jmx:name=Scheduler,service=scheduler">
 <constructor>
 <arg type="java.lang.String" value="jboss.jmx"/>
 <arg type="java.lang.String" value="service"/>
 <arg type="java.lang.String" value="Timer"/>
 </constructor>
 <depends>jboss.j2ee:module=app-ejb.jar,service=EjbModule</depends>
 </mbean>

and the application xml is as follows

 <application>
 <display-name>app-name</display-name>
 <description>Devel Application</description>
 <module>
 <ejb>app-ejb.jar</ejb>
 </module>
 <module>
 <ejb>app-scheduler.sar</ejb>
 </module>
 <module>
 <web>
 <web-uri>app-test.war</web-uri>
 <context-root>/app-test</context-root>
 </web>
 </module>
 <module>
 <web>
 <web-uri>app.war</web-uri>
 <context-root>/app</context-root>
 </web>
 </module>
 </application>

yet still the app-scheduler.sar is deployed befpre the app-ejb.jar.

Any other ideas? I am using jboss 3.2.3 but thinking of upgrading to 3.2.6 to see if that solves the problem. Truly stuck here!

thanks again

Murray