Bugs item #557836, was opened at 2002-05-18 19:53
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=557836&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Brian Topping (topping)
Assigned to: Nobody/Anonymous (nobody)
Summary: DeploymentException: InputStream cannot
Initial Comment:
Cannot deploy a seemingly well-formed EAR file, whose
component WAR/JAR files will independently deploy
without problems. Scott asked me to upload this to
track/resolve it.
----------------------------------------------------------------------
>Comment By: Scott M Stark (starksm)
Date: 2002-05-18 20:15
Message:
Logged In: YES
user_id=175228
In both RC2 and the latest 3.0 cvs I see the same exception
and this is not an InputStream exception. The exception is:
20:12:09,390 INFO [EARDeployer] Init J2EE application:
file:/D:/usr/local/src/c
vsroot/JBoss3.0/jboss-all/build/output/jboss-
3.0.0RC3/server/default/deploy/samp
les.ear
20:12:09,437 ERROR [EARDeployer] Error in init step of ear
deployment
org.jboss.deployment.DeploymentException: url
njar:file:/D:/usr/local/src/cvsroo
t/JBoss3.0/jboss-all/build/output/jboss-
3.0.0RC3/server/default/tmp/deploy/serve
r/default/deploy/samples.ear/76.samples.ear^//samples-
web.war could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.<init>
(DeploymentInfo.java:167)
at org.jboss.deployment.EARDeployer.init
(EARDeployer.java:153)
at org.jboss.deployment.MainDeployer.init
(MainDeployer.java:570)
at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:515)
at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:490)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke
(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:491)
at org.jboss.util.jmx.MBeanProxy.invoke
(MBeanProxy.java:174)
at $Proxy4.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy
(URLDeploymentScanner.java:405)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scanDirect
ory(URLDeploymentScanner.java:586)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan
(URLDeploymentScanner.java:465)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$Scann
erThread.loop(AbstractDeploymentScanner.java:202)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$Scann
erThread.run(AbstractDeploymentScanner.java:191)
The problem is the leading / in the web-uri and ejb element
jar value. These need to be relative uris. Using this
application.xml allows deployment to succeed:
557836 872>cat META-INF/application.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE application PUBLIC '-//Sun Microsystems,
Inc.//DTD J2EE Application 1.
2//EN' 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
<application>
<display-name>
Samples
</display-name>
<module>
<web>
<web-uri>
samples-web.war
</web-uri>
<context-root>
/samples
</context-root>
</web>
</module>
<module>
<ejb>
samples-ejb.jar
</ejb>
</module>
</application>
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=557836&group_id=22866
_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
