Aaron,
> BTW, how does the updated J2eeDeployer handle multiple EJB JARs in
> an EAR?
It _can_ handle them right now.
Did you use such a scenario? Actually that should not have been
possible?!
> Are they all on the same ClassLoader? Does the WAR see them
> all? Or is this just not allowed?
Its as I said in the previous mail.
The .war files that will interact with ejb files must have a Class-Path
entry in their MANIFEST.MF that points to the package(s) that contain
the remote interfaces (and other for communication needed classes) for
the ejb packages. All files that are referenced by
MANIFEST.MF/Class-Path entries will be loaded by the common classloader.
The mentioned interface packages are just the <file>-client.jar packages
that every good bean developer will create for its ejb archive, as
Rickard pointed out.
Hope that answers your question.
\Daniel
