I know you don't want to read long stack traces, so here's the synopsis:

jboss-4.0.5 has problems resolving three jbossws jars.

I've noticed several posts calling attention to this problem, but have not 
found references to any resolutions.


  | 2006-11-28 14:18:13,260 DEBUG [org.jboss.deployment.MainDeployer] 
resolveLibraries: jaxb-api.jar activation.jar jsr173_1.0_api.jar jaxb1-impl.jar
  | 
I installed jboss-4.0.5 with the "jems-installer".  The configuration is 
"ejb-clustered" and named  "default".

Here are some relevant portions of the stack trace:


  | 2006-11-28 14:18:12,668 DEBUG [org.jboss.deployment.JARDeployer] looking 
for nested deployments in : 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb-impl.jar
  | 2006-11-28 14:18:13,257 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] 
Added url: 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/tmp/deploy/tmp8839jaxb-impl.jar,
 to ucl: [EMAIL PROTECTED] 
url=file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/ 
,addedOrder=12}
  | 2006-11-28 14:18:13,260 DEBUG [org.jboss.deployment.MainDeployer] 
resolveLibraries: jaxb-api.jar activation.jar jsr173_1.0_api.jar jaxb1-impl.jar
  | 2006-11-28 14:18:13,260 DEBUG [org.jboss.deployment.MainDeployer] new 
manifest entry for sdi at jaxb-impl.jar entry is jaxb-api.jar
  | 2006-11-28 14:18:13,260 DEBUG [org.jboss.deployment.MainDeployer] new 
manifest entry for sdi at jaxb-impl.jar entry is activation.jar
  | 2006-11-28 14:18:13,267 DEBUG [org.jboss.deployment.MainDeployer] The 
manifest entry in 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb-impl.jar
 references URL 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/activation.jar
 which could not be opened, entry ignored
  | 2006-11-28 14:18:13,277 DEBUG [org.jboss.util.NestedThrowable] 
org.jboss.util.NestedThrowable.parentTraceEnabled=true
  | 2006-11-28 14:18:13,277 DEBUG [org.jboss.util.NestedThrowable] 
org.jboss.util.NestedThrowable.nestedTraceEnabled=false
  | 2006-11-28 14:18:13,278 DEBUG [org.jboss.util.NestedThrowable] 
org.jboss.util.NestedThrowable.detectDuplicateNesting=true
  | org.jboss.deployment.DeploymentException: url 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/activation.jar
 could not be opened, does it exist?
  |     at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214)
  | 
  | 
  | 2006-11-28 14:18:13,285 DEBUG [org.jboss.deployment.MainDeployer] new 
manifest entry for sdi at jaxb-impl.jar entry is jsr173_1.0_api.jar
  | 2006-11-28 14:18:13,285 DEBUG [org.jboss.deployment.MainDeployer] The 
manifest entry in 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb-impl.jar
 references URL 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jsr173_1.0_api.jar
 which could not be opened, entry ignored
  | org.jboss.deployment.DeploymentException: url 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jsr173_1.0_api.jar
 could not be opened, does it exist?
  | 
  | 
  | 2006-11-28 14:18:13,291 DEBUG [org.jboss.deployment.MainDeployer] new 
manifest entry for sdi at jaxb-impl.jar entry is jaxb1-impl.jar
  | 2006-11-28 14:18:13,292 DEBUG [org.jboss.deployment.MainDeployer] The 
manifest entry in 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb-impl.jar
 references URL 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb1-impl.jar
 which could not be opened, entry ignored
  | org.jboss.deployment.DeploymentException: url 
file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb1-impl.jar
 could not be opened, does it exist?
  | 

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989498#3989498

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989498
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to