Solved it by commenting loader-repository in jboss-app.xml and didn't meet problems with deployment on startup as in the first post in the thread.
But what's wrong with loader-repository? alex Monday, August 12, 2002, 8:12:27 PM, you wrote: AL> Hello Burkhard and all, BV>> Hmmm, BV>> For a start put the mysql jar from the META-INF dir to the root dir of the BV>> sar... AL> Sorry, I wrongly pictured the ear's structure. Here is the correct one. AL> dbdrvsar.ear: AL> META-INF/ AL> META-INF/MANIFEST.MF AL> META-INF/application.xml AL> META-INF/jboss-app.xml AL> dbdrvsar-web.war AL> dbdrvsar.sar AL> dbdrvsar-ejb.jar AL> dbdrvsar.sar: AL> META-INF/ AL> META-INF/MANIFEST.MF AL> META-INF/jboss-service.xml AL> mm.mysql-2.0.6.jar AL> jboss-app.xml AL> <jboss-app> AL> <loader-repository>org.leisi:loader=dbdrvsar.ear</loader-repository> AL> <module> AL> <service>dbdrvsar.sar</service> AL> </module> AL> </jboss-app> AL> Successful attempts: AL> - driver's jar in the lib and driver's -service.xml in the deploy; AL> - separated sar with driver's jar and -service.xml deployed fine and AL> then the ear deployed fine with removed jboss-app.xml and AL> dbdrvsar.sar. AL> JBoss version is 3.0.2RC1. -- Best regards, Alex Loubyansky ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
