Having to nest jars in a particular manner to achieve the correct deployment ordering certainly is not simple. Here your talking about the static deployment directories while all of the current issues are with self-contained deployment units of j2ee components and services. We need a simple mechanism for handling the ordering of component deployment within a xar.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "marc fleury" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 12, 2002 6:56 PM Subject: [JBoss-dev] ordering proposal > ok, it is 3 am in london and i drank a bit too much beer with jules and > sacha.... > > however, > > can't we simply do a > > deploy/first/ > > deploy/second/ > > deploy/third/ > > a la 'init.d/rc1-2-3' > > and we first deploy the stuff from 'first' then 'second' then 'third' > > so we can **********simply************ explain to people that if they need > something first then they put it in first, then if they need something in > second they put it in second. > > simple... > > simple to explain > > a bit more complex to code but would be worth it... > > marcf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
