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 onc
I was just looking
through the source in the Installer.java file and came across the same
conclusion!The problem is the manifests that are inspected are in
the war and jar files, not the ear files.Thanks for the
response!jimTo: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>cc: Subject: RE:
[JBos
Hi,
> -Original Message-
> From: James Cook [mailto:[EMAIL PROTECTED]]
>
> According to the following documentation, jBoss includes the
> ability to deploy
> library archives in an ear file.
>
> http://www.jboss.org/documentation/HTML/ch10s71.html#N37d7
>
> "On deployment one - common
According to the following documentation, jBoss includes the ability to deploy
library archives in an ear file.
http://www.jboss.org/documentation/HTML/ch10s71.html#N37d7
"On deployment one - common - classloader is created. This classloader will get
all archives in its classpath that are refere
