An error is throw by JBoss 4.0.5 server when deploying a web-app with SEAM-1.1.0/lib/thirdparty-all.jar placed in WEB-INF/lib directory. The same error is reported in:
caused by the presence of log4j and common-logging jars in the thirdparty-all.jar.
So, thinking about this type of conflicts that may occur, does the use of thirdparty-all.jar must be encouraged?
You don't need to use thirdparty-all.jar when deploying to jboss as - it's just a wrapped up set of all the libraries that jboss provides but other environments don't.