I thought this worked in alpha (can't remember having any problem with datasource and jars)?
If all .sar's (datasources) are deployed before the .jar's, it will solve my problem. Are there any dependencies at deploy time between .jars with beans and ejb-jar.xmls? ejb-links? Isn't most dependencies dicovered when running the beans? (if not, this should be a issue for the 2.x-versions too). Does it take too much time too scan all xml-files in all .?ars first to find the right order? Also if we need to specify dependencies ourself, it is easier to specify in every bean what other ?jar it depends on instead of renumbering the order (renaming many files). Another idea could be to check the timestamps of the files and deploy them in the order they have been deployed the first time. This won't work if some modules is redeployed though. (This is just my opinions on this from a jboss user perspective) Marius On Sat, 2002-03-16 at 15:47, Peter Fagerlund wrote: > on 15-03-2 22.05, David Jencks at [EMAIL PROTECTED] wrote: > > > My opinion still is that handling this automatically is the best solution, > > by converting every kind of dependency into an mbean dependency. If we get > > people used to numbering their files, then they will have a delightful > > opportunity to number them in an order different from that required by an > > actual dependency analysis. > > Yes - automagic is simpler yet very much more complex - economical tho at a > higher initial price ... > > Could ANT genjar http://www.riggshill.com/projects/genjar/ help with > filtering classes in a dependency phase ? ... > > /peter_f > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development
signature.asc
Description: This is a digitally signed message part
