[webbeans-dev] wb-ri-int deployers tests

Ales Justin ales.justin at gmail.com
Wed Jul 15 08:40:29 EDT 2009


Just a simple update on what I've been doing with WBINT.

Due to the two issues:
(a) WBINT-15; does auto CL isolation really work?
(b) WBINT-16; wrapped WB war in ear doesn't work

I first checked (b), which confirmed a bug in how we did dynamic 
classpath addition.

In order to do proper CL testing, I needed to move tests + support code 
under org.jboss.test.deployers packages, since that's how our MC 
BootstrapTest knows which classes to exclude.
e.g. the test can of course get a hold of test classes,
but that doesn't mean that they should leak into the deployments we test

Since we add WB Bootstrap bean into top level deployment,
that top level needs to see wb-core.jar (which is what wasn't happening 
with WBINT-16).

Hence the split into 2 URLIntegrationDeployers:
(1) one that adds wb-core.jar to top level if any beans.xml is found
(2) another that adds faces/ to any web deployment + beans.xml is found 
in metadata locations

For (a) I added new CLIsolationTestCase, which actually proved that the 
automatic CL isolation worked properly.
Or, at least the deployers we have, are kicking in as they should.
But this is still an issue to be tested in a real JBossAS env - 
something Shelly is working on.

-Ales



More information about the weld-dev mailing list