Unfortunately there isn't any nice solution. But a bit of a hack is provided in
conf/jboss-service.xml
You need to comment out the DeploymentSorter below, and use the PrefixDeploymentSorter
commented out just below it, like this.
<!--
org.jboss.deployment.DeploymentSorter
-->
org.jboss.deployment.scanner.PrefixDeploymentSorter
Now on deployment you'll have to prefix your ears with numbers:
001_common.ear
002_app1.ear
003_app2.ear
etc...
This will ensure common.ear will be deployed before any of the other two (but AFTER
any ear without the number prefix)
Personally I thought this was such an ugly solution that I first refused to use it.
Until I had no choice any longer, and it works fine. But it's rather disappointing
there isn't a way to put order information in the jboss.xml files, it seems so much
more logical.
Something like:
common.ear,common.sar,whatever.jar
to indicate that other archives need deploying first shouldn't have been so hard to
make I would have thought.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849778#3849778
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849778
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
