Description of problem:
slf4j libs were removed from jboss-brms.war/WEB-INF/lib to resolve bug 724487, but that prevents the webapp from deploying into EWS where these libs are not provided. Can be easily solved by adding slf4j-api and slf4j-log4j12 into jboss-brms.war/WEB-INF/lib but this is a manual step that should be documented in the BRMS Administrator Guide. Also, the missing slf4j libs should be part of the brms-deployable package, so that the product is shipped with all necessary components.
Version-Release number of selected component (if applicable):
JBoss EWS 1.0.2
deployment fails due to
Aug 19, 2011 1:22:53 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class org.drools.guvnor.server.repository.RepositoryShutdownService
the missing libs should be shipped, manual configuration steps must be documented
slf4j-api is already in brms-engine.zip.
I would add slf4j-log4j12 into brms-engine.zip from next release(ER4 or CR1). This action would also fix Bug 734066 (- slf4j is missing classes on IBM JVM).
Darrin,Could you do the documentation part of this issue? Thanks in advance.
Add one more step for deploying jboss-brms.war into EWS.
Copy slf4j* from jboss-brms-engine.zip/binaries/ to jboss-brms.war/WEB-INF/lib
(In reply to comment #1)
> Darrin,Could you do the documentation part of this issue? Thanks in advance.
I don't think Darrin works on BRMS anymore. CCing Lee.
You're quite right, Darrin has moved on to another product.
I'll add the information to the admin guide shortly.
Update this issue now.
The underlying BZ is not fixed, which means this one is not as well. But the documentation part is OK.
It is fixed now. Please verify it in the next Release.
Underlying issue is fixed, marking as VERIFIED.