I'm putting the classpath entries in the manifest of the ejb jars. The bug you
referenced is about putting classpath entries in the mainfest of the ear so I
don't think it is the same thing. The J2EEDeployer seems to pick up these
entries fine. I've even written a test classloader that loads shared classes
fine through the ejb jar so I know the jars are correct.
Richard Backhouse
Juha Lindfors wrote:
> Verifier uses the classloader it gets from container factory. Are you
> adding your shared classes in the ejb jar manifest or are you using ears?
>
> There's a bug related to this in bugzilla #223, is this the same issue?
>
> -- Juha
>
> >On Thu, 7 Dec 2000, Richard Backhouse wrote:
> >> I have changed the packaging of my app to better use the shared classes
> >> between archives. In doing this I found
> >> that while the J2eeDeployer picks up on the Class-Path entries in
> >> archives and puts them in the classpath the
> >> verifier doesn't seem to be using the same classloader when it tries to
> >> verify the ejb jars in the ear. I get
> >> ClassNotFoundExceptions.
> >>
> >> Bug ?
