Hi,
I have finally managed to fix issue 32. The default configuration that
scans for classes in WEB-INF/classes and jars in WEB-INF/lib should
now be fully portable. Special thanks to Gerard for providing a
prototype proof of concept.
I have tested on GlassFish v2.1, the latest GlassFish v3, Tomcat 6.0
and JBoss 5.1.0.GA. Would it be possible for others to verify on
WebLogic and WebSphere?
Attached is a simple maven-based project to aid testing. This consists
of a parent project and two child projects. The first child is a jar
project that produces a jar with one root resource class. The second
child is a war project that includes the jar of the first child in WEB-
INF/lib and one root resource class in WEB-INF/classes.
I have also managed to fix issues with package scanning deployment on
JBoss 5.x. For those of you using JBoss 5.x it would be most helpful
if you could verify deployments work for the case of deploying war
files are not expanded (and also check for regressions for the case
when war files are expanded).
IIRC there have been some issues on other app servers like Resin. The
code is now reasonably flexible it might be possible to support
additional app server-specific scanning support. Thus for those using
other app servers i encourage you to log issues.
Hopefully there are not any regressions, but we have plenty of time to
fix issues before we release 1.1.5.
It is probably going to take a couple of hours for Hudson to build and
for the new 1.1.5-ea-SNAPSHOT artifacts to get pushed to the repo. So
if you want to verify sooner you need to check out the trunk and build.
Note that i have completely re-factored the scanning functionality. It
is almost possible to reuse this on the client side as i know some
developers want a package-scanning-based ClientConfig. It requires
that the ASM dependency and the AnnotationScannerListener class move
from jersey-server to jersey-core.
Paul.