"gudmundsonsc" wrote : Write your own DeploymentSorter. You certainly can do this. Having done it I can't say I recommend it. The way we went was to maintain a global deployment ordering list and sort based on that. It is a pain in the ass to maintain this.
Using the PrefixDeploymentSorter is another option, you just have to name your deployed files 01xxx.ear,02yyy.war, etc.. Of course this is really just the same as above. What I think would be real nice is to be able to define dependencies in the deployment descriptors contained in the war/ear/jar files (or somewhere like that) so that the deployment ordering is flexible and a component only has to specify it's own requirements and you don't need a global ordering defined (as in the above two solutions). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838734#3838734 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838734 ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
