Michael Golubev created TOMEE-223:
-------------------------------------
Summary: An archive artifact is not deployed when using deployment
descriptor
Key: TOMEE-223
URL: https://issues.apache.org/jira/browse/TOMEE-223
Project: TomEE
Issue Type: Bug
Reporter: Michael Golubev
I experience problems with deployment of archive artifacts (WARs and EARs) to
TomEE 1.0.0.
An archive artifact is not deployed (as I expect) when deployment descriptor is
placed into <TomEE home>/conf/Catalina/localhost folder.
Exactly the same workflow works for exploded artifacts.
Exactly the same workflow (for WAR's) works for both archive and exploded
artifcats in just-a-Tomcat.
I am developing an integration for TomEE and IntelliJ IDEA and can not easily
workaround by using different deployment methods.
WAR case:
- deployment descriptor:
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/myWarCtx" docBase="C:\path\to\myWar.war" />
- error message:
java.lang.IllegalStateException: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/myWarCtx]]
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:898)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
at
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
at
org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1585)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
EAR case:
- deployment descriptor:
<?xml version="1.0" encoding="UTF-8"?>
<Context docBase="C:\path\to\myEar.ear" />
- error message:
java.lang.IllegalArgumentException: Document base C:\path\to\myEar.ear
does not exist or is not a readable directory
at
org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:140)
at
org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4894)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5074)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
at
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
at
org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1585)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
WAR case looks like obvious downgrade from essential Tomcat, since deployment
with the sample deployment descriptor on Tomcat is successful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
