[jboss-user] Deployment errors when JARs contain XML files in META-INF
I have been running JBoss 3.2.7 with an exploded EAR installed in
jboss3/default/deploy, and it has been working fine. Now I want
to run it with the exploded EAR somewhere else (to save time copying
the files during development). So I changed the URLs entry in
jboss3/default/conf/jboss-service.xml from this:
<attribute name="URLs">
deploy/
</attribute>
to this:
<attribute name="URLs">
file:///c:/src/4_1_2/bc/build , deploy/
</attribute>
(I also tried reversing the order of those 2 items or just
using the build dir).
Most of the deployment seems to go OK but then I get these errors:
07:56:05,035 ERROR URLDeploymentScanner - Incomplete Deployment listing:
Packages waiting for a deployer:
org.jboss.deployment.DeploymentInfo@6234bac5 {
url=file:/c:/src/4_1_2/bc/build/jdom.jar }
deployer: null
status: Starting
state: START_SUBDEPLOYMENTS
watch: file:/c:/src/4_1_2/bc/build/jdom.jar
lastDeployed: 1169567649949
lastModified: 1169567649949
mbeans:
org.jboss.deployment.DeploymentInfo@9aa4060a {
url=file:/c:/src/4_1_2/bc/build/jwebunit-core-1.3.jar }
deployer: null
status: Starting
state: START_SUBDEPLOYMENTS
watch: file:/c:/src/4_1_2/bc/build/jwebunit-core-1.3.jar
lastDeployed: 1169567650121
lastModified: 1169567650121
mbeans:
org.jboss.deployment.DeploymentInfo@fd52bd88 {
url=file:/c:/src/4_1_2/bc/build/jwebunit-htmlunit-plugin-1.3.jar }
deployer: null
status: Starting
state: START_SUBDEPLOYMENTS
watch: file:/c:/src/4_1_2/bc/build/jwebunit-htmlunit-plugin-1.3.jar
lastDeployed: 1169567650121
lastModified: 1169567650121
mbeans:
Interestingly, these 3 JARs are the only non-EJB JARs with XML files
in the META-INF dir:
jdom.jar ->
META-INF/info.xml
jwebunit-core-1.3.jar ->
META-INF/maven/net.sourceforge.jwebunit/jwebunit-core/pom.xml
jwebunit-htmlunit-plugin-1.3.jar ->
META-INF/maven/net.sourceforge.jwebunit/jwebunit-htmlunit-plugin/pom.xml
I read in another forum about this bug and it suggested removing
info.xml from jdom.jar, but I really don't know what effect removing
these files from these JARs will have so I would prefer a better
solution to this problem. It seems like a bug in JBoss.
It's strange it only showed up when I changed the deploy location.
Thanks,
Dan