The class-path entry in the manifest of bean deployer's jars
(jboss-container.jar, jboss-microcontainer.jar) include references to:
Class-Path: jboss-common.jar log4j.jar concurrent.jar xercesImpl.jar .
./conf/
Those libs are then looked up in .../deploy/jboss-bean.deployer/,
producing ignored DEBUG exceptions in the log file.
Can we avoid them?
2005-08-05 21:59:03,332 DEBUG [org.jboss.deployment.MainDeployer] new
manifest entry for sdi at jboss-microcontainer.jar entry is
jboss-common.jar
2005-08-05 21:59:03,332 DEBUG [org.jboss.deployment.MainDeployer] The
manifest entry in
file:/X:/cvs/jboss-public/jboss-4.0/build/output/jboss-4.0.3RC2/server/a
ll/deploy/jboss-bean.deployer/jboss-microcontainer.jar references URL
file:/X:/cvs/jboss-public/jboss-4.0/build/output/jboss-4.0.3RC2/server/a
ll/deploy/jboss-bean.deployer/jboss-common.jar which could not be
opened, entry ignored
org.jboss.deployment.DeploymentException: url
file:/X:/cvs/jboss-public/jboss-4.0/build/output/jboss-4.0.3RC2/server/a
ll/deploy/jboss-bean.deployer/jboss-common.jar could not be opened, does
it exist?
at
org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:175)
at
org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.ja
va:1085)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:839)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:847)
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
