> > >this is great, this is today in cvs, unless a certain someone removed this >as well. >
=P >The problem is a painful russian doll structure. > >3- however there are 3 static directories deploy/first, deploy/second, >deploy/third, actually i could call them >deploy/deploy1, deploy/deploy2/deploy3... and allow for arbitrary numbers >but we would provide at least 3. >AND >if you drop something in deploy and deploy1 deploy2 for example > >deploy/sar >deploy1/jar >deploy2/war, sar1 >deploy3/ jar2, ear, xml > >you get > >deploy1-deploy2-deploy3-deploy with ordering from 2 and 1 above so > >jar, sar1, war, jar2, xml, ear, sar > So, if I have an ejb-jar which depends on some code deployed from an xml, which is all used by a service deployed by a sar... where do my files go? This may simplify the code which has to deal with depdenencies... by basically avoiding the problem... but it complicates the user configuration... >voila! no dependency explicitely set but a very simple way of putting stuff >in the right order. It will do the trick. I'll code it if a certain someone >doesn't. > With the recent mod to UDS this will work... just list new directory urls in jboss-service.xml. >rc1-rc6 has been in Unix for 20 years, so let's stop fucking around > Um... ya... well there have already been several others who have commented on this... lets not get confused over runlevels and Sn|Kn ordering... which are there only because the system does not have the capacity to define or ask the services started from the script what the dependecies are. The problem of solving the dependecies automatically inside of the server aren't really that huge... just a bit tricky here and there. We are almost there, with the depends element... but we need to finish off the job... by extending that to j2ee deployables (which can be done by adding support and config to jboss.xml) and by changing the system to wait for all dependencies to be meet before attempting to install any of the service into the spine. Perhaps dependecies should be rethought all together... not that I particularly want to spend any time there... but perhaps someone should. In the mean time I don't think we should move the complexity on to configuration/users. Short-term, sorting ala UDS for scanned directories is enabled. This should fix the issues we have seen... --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
