So the manifest in the EJB's (which I saw is sorta doc'd in the EJB spec) can
indicate a classpath. When jBoss (and hopefully, any J2EE-compliant container)
encounters these classes, they get added to the current classpath. Great! This
allows a developer to include a set of shared classes only once in an ear file.
Super!

But...

What happens if I want to use this technique when deploying a single EJB
archive? If I add the shared libs to the ejb archive file and specify a manifest
file that references them, jBoss attempts to add the libraries and fails. Is
this a bug, or is it supposed to work this way?

thanks,
jim


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to