geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Williams (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1445) Allow deployment and use of exploded EAR modules
Date Tue, 10 Jan 2006 00:24:26 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1445?page=comments#action_12362270 ] 

Todd Williams commented on GERONIMO-1445:
-----------------------------------------

Aaron,

You're correct in that this is the exploded war in the exploded ear case and does not currently
work.  
In addition, I also think it would be desirable for exploded EJB jars within an exploded EAR
to work as well so that
one can deploy a completely exploded EAR (with whatever in it) and have it work just like
the packaged version.
Thanks for your prompt comments and attention to this.

> Allow deployment and use of exploded EAR modules
> ------------------------------------------------
>
>          Key: GERONIMO-1445
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1445
>      Project: Geronimo
>         Type: Bug
>   Components: deployment, Hot Deploy Dir
>     Versions: 1.0
>  Environment: Windows XP
>     Reporter: Todd Williams
>     Assignee: Aaron Mulder
>      Fix For: 1.0.1, 1.1
>  Attachments: GeronimoTestEar.ear.zip
>
> Using the Geronimo 1.0 / Tomcat bundle, placing an exploded WAR into the deploy  directory
causes it to be picked up and deployed by the hot deployer as expected.  However, if I wrap
the exploded war with an exploded EAR, Geronimo fails to deploy  with the error message :
> 17:00:50,282 INFO  [Hot Deployer] Deploying GeronimoTestEar.ear
> 17:00:51,494 ERROR [Hot Deployer] Unable to deploy: Module was not a war: GeronimoTestWeb.war
> org.apache.geronimo.common.DeploymentException: Module was not a war: GeronimoTestWeb.war
> 	at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:544)
> 	at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:226)
> 	at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:122)
> 	at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(<generated>)
> 	at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> 	at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> 	at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118)
> 	at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800)
> 	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
> 	at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36)
> 	at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
> 	at org.apache.geronimo.deployment.ConfigurationBuilder$$EnhancerByCGLIB$$1c79c440.getDeploymentPlan(<generated>)
> 	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:219)
> 	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102)
> 	at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(<generated>)
> 	at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> 	at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> 	at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118)
> 	at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835)
> 	at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178)
> 	at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:106)
> 	at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:59)
> 	at java.lang.Thread.run(Thread.java:534)
> I'll attached a zip that when unzipped contains the exploded hierarchy for the EAR. 
The application is small, but valid, as it deploys just fine when created as an archived EAR.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message