Bugs item #523060, was opened at 2002-02-26 10:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=523060&group_id=22866
Category: JBossServer Group: v3.0 Rabbit Hole Status: Deleted Resolution: Duplicate Priority: 5 Submitted By: Jim Cook (oravecz) Assigned to: David Jencks (d_jencks) Summary: EJB's in EAR files - Classpath Failure Initial Comment: When an EJB is packaged, its manifest file may reference another library using its Classpath attribute. If the EJB is deployed, the jar's referenced by the manifest are resolved using the JAR as the root. If the EJB JAR is packaged in an EAR file, the Classpath attribute for the EJB JAR should be resolved relative to the *EAR* file. This is not happening in jBoss 3.0 Beta. With the new /tmp flat directory filenaming scheme, it is not apparent to me how any jars in a classpath manifest can be located. This is due to the libraries being prefixed with a number (i.e. 47.ejbhelper.jar) and represented in a flat structure. Under these circumstances how can a manifest classpath of './lib/ejbhelper.jar' ever be found? ---------------------------------------------------------------------- >Comment By: Jim Cook (oravecz) Date: 2002-02-26 14:16 Message: Logged In: YES user_id=6215 So any jar file anywhere in my ear directory structure is exposed to my EJBs that are contained in the jar? This approach doesn't seem to violate 23.4 (EJB 2.0 FR), but there should be some clear documentation on how class/package conflicts are resolved. ---------------------------------------------------------------------- Comment By: marc fleury (mnf999) Date: 2002-02-26 10:48 Message: Logged In: YES user_id=174548 Yeah in fact we should clearly state that the manifest entries are fully ignored. And maybe only log a debug message about it. It seems to confuse people when it is in fact working correctly due to the Unified Deployers pick of classes marcf ---------------------------------------------------------------------- Comment By: David Jencks (d_jencks) Date: 2002-02-26 10:27 Message: Logged In: YES user_id=60525 Look before you leap. This is the same issue as 520676, which was fixed shortly after jboss beta. The manifest references are pretty much ignored, but all the classes are loaded anyway. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=523060&group_id=22866 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
