That's usually what I've done but that adds another file (manifest) and changes the build script and then you've got to repeat that for all the jars that use common.jar. It seems like a lot of needless tinkering when it should just load jars in the base of the ear listed as "java" modules.
In fact JBoss does load "java" modules whether they contain a client application or not. Maybe it's a bug but it's VERY convenient. Only thing is the load order isn't specified, but it seems to work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932845#3932845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3932845 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
