>
> ....
> snapshots of JBoss. The issue is that the Verifier's ClassLoader's
> classpath points only to its own EJB, while in a multiple EJB-jar EAR, all
> the EJB-jars have to be in the ClassLoader's classpath. There seems to
> have been an attempt to fix this in the current snapshot but not fully --
> the J2eeDeployer adds all the EJB jars to the common classpath but when it
> comes to deploying individual jars, there is still the same classpath
> issue.
>
David Castro wrote:
>
> what?? why should ejb jars be in the common classpath?? that is not
> accurate.
>
> Shared classes (such as remote interfaces) should be in the common classpath
> by putting them in a shared jar. ejb jars should only be visible to the ejb
> that uses them.
>
> Try putting classes private to the ejb in the ejb-jar, and shared classes in
> a shared jar. that is how I fixed the classloading problem.
>
The empirical test of whether the JBoss implementation is correct is this:
Can the Pet Store 1.1.1 .ear be deployed in JBoss by making changes to
the deployment descriptors? (The Pet Store can in no way be considered
a trivial application.)
Right now, the answer is "No", so it would seem to me that JBoss deployment
needs some work.
Tom
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
