We tend to make self-contained deployers. When bundling in jbossas only
the implementation should be in the .deployer. The javaee classes should
be in the server/lib dir.
Dimitris Andreadis wrote:
I see a mix-up in our libraries, that leads to classloading errors
in
the testsuites (see in
the bottom):
- sun-servlet in thirdparty was v2.4, although jboss-web comes with it's
own servlet-api
jars at v2.5. I changed thirdparty to v2.5, too
- jboss-ejb3x in deploy/ejb3.deployer/ should really be in
server/xxx/lib, right? (I have
moved it).
- jboss-ejb3x and jboss-web.deployer/annotations-api.jar contain *some*
duplicates (I think
this causes the classloading errors). Unless we are going to create a
new shared module, I
believe we need to add the missing source code in our ejb3x module and
not deploy
annotations-api.jar
- server-api.jar, jsp-api.jar, el-api.jar. We could have only one copy
of them in the
server/xxx/lib directory, and not have it also tin the
jboss-web.deployer/ dir
Comments/Suggestions?