Let me refine my last post. I believe it is the specification's intention that "normal" utility jars in an ear are available for inclusion in a classpath, but should not be included in that classpath by default.
So framework.jar can be roped in to someone else's classpath by way of a MANIFEST.MF Class-Path: entry, but should NOT be dumped into a classpath by default. For that matter--and I freely admit ignorance here--why does the ear loader need a classpath inside it at all? It seems that one must be in place. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941363#3941363 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3941363 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
