OK, thanks for the info. I hope to at least implement a soltuon using a deploy order implementation (a solution from Sacha, thanks!) that simply adds the war filter after the ear, and see if I have another solution in the foe servers. Sounds like the apache commons digester or Castor *might* help with that random issue, since they use SAX (and may then fire the events in order of the XML rather than produce a random list) to call the digester rules. Since it's a one-way read, it may offer an ordered deployment, but can't recall if the specs say that this is required or not and if I'm right about those 3rd party libs or not (I'm tired and lazy to find out right now). If its not a spec requirement, then I'm sure this isn't a priority and I don't have a chance of getting a x-server solution through the application.xml anyway.
Thanks again, James > -----Original Message----- > From: Jason Dillon [mailto:[EMAIL PROTECTED]] > Sent: Saturday, October 05, 2002 9:33 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] Over zealous deployers > > > Again, I am not positive, but I believe the order is > determined by the XML > impl, when it returns a NodeList. From what I can tell the > order is fairly > random. > > The only way I could get deployments to order correctlt was > to use the JBoss > <depends> tag (in jboss.xml in each of the members of the > EAR) and depend on > the dependent deployed services in the other JAR files. > > --jason > > > > Actually, this brings up a question I've meant to ask for a while - > > how do you guys determine the order for which modules are deployed > > when declared in an application.xml file? I had asked a few > days ago > > how to control the order of deployment of ears and wars (currently > > separate in the deploy dir). But, without changing my > deploy scripts > > in Ant, I wanted to see what the algorithm was (or where the code > > lives) that determines the order. I was thinking that if > the war was > > defined last in the application.xml, it might get deployed last and > > thus my cheezy, x-appserver SessionContextListener would fire after > > all EJBs are deployed (Mbeans are out, as I don't have good mbean > > support in the jboss foe servers). > > > > Thanks, > > James > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Jboss-development mailing list > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
