tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <>
Subject [jira] [Created] (MTOMCAT-193) Odd need to create an empty context.xml file for the Apache Tomcat Maven plugin to work
Date Sat, 08 Dec 2012 19:53:20 GMT
Glen Mazza created MTOMCAT-193:

             Summary: Odd need to create an empty context.xml file for the Apache Tomcat Maven
plugin to work
                 Key: MTOMCAT-193
             Project: Apache Tomcat Maven Plugin
          Issue Type: Bug
          Components: tomcat7
    Affects Versions: 2.0
         Environment: Ubuntu Linux, JDK 7, CXF 2.7.1
            Reporter: Glen Mazza
            Assignee: Olivier Lamy (*$^¨%`£)
            Priority: Minor

Hi, I switched from the Codehaus to the Apache Tomcat plugin for Apache CXF's REST archetype:

For "mvn clean install" to work with the new plugin I needed to add an empty META-INF/context.xml

This file was never needed by the Codehaus plugin.  If I didn't add it for the Apache one,
"mvn clean install" returns this error:

[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ testrest ---
[INFO] Skipping execution of surefire because it has already been run for this configuration
[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ testrest ---
[INFO] Packaging webapp
[INFO] Assembling webapp [testrest] in [/media/work1/opensource/testrest/target/testrest-0.0.1-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/media/work1/opensource/testrest/src/main/webapp]
[INFO] Webapp assembled in [29 msecs]
[INFO] Building war: /media/work1/opensource/testrest/target/testrest-0.0.1-SNAPSHOT.war
[INFO] WEB-INF/web.xml already added, skipping
[INFO] <<< tomcat7-maven-plugin:2.0:run-war (start-tomcat) @ testrest <<<
[INFO] --- tomcat7-maven-plugin:2.0:run-war (start-tomcat) @ testrest ---
[INFO] Running war on http://localhost:56114/jaxrs-service
[INFO] Creating Tomcat server configuration at /media/work1/opensource/testrest/target/tomcat
[INFO] create webapp with contextPath: /jaxrs-service
Dec 08, 2012 2:37:48 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-56114"]
Dec 08, 2012 2:37:48 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Tomcat
Dec 08, 2012 2:37:48 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.30
Dec 08, 2012 2:37:48 PM org.apache.catalina.startup.ContextConfig processContextConfig
SEVERE: Missing context.xml: file:/media/work1/opensource/testrest/target/testrest-0.0.1-SNAPSHOT/META-INF/context.xml /media/work1/opensource/testrest/target/testrest-0.0.1-SNAPSHOT/META-INF/context.xml
(No such file or directory)
	at Method)
	at org.apache.catalina.startup.ContextConfig.processContextConfig(
	at org.apache.catalina.startup.ContextConfig.contextConfig(
	at org.apache.catalina.startup.ContextConfig.init(
	at org.apache.catalina.startup.ContextConfig.lifecycleEvent(
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
	at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(
	at org.apache.catalina.util.LifecycleBase.setStateInternal(
	at org.apache.catalina.util.LifecycleBase.init(
	at org.apache.catalina.util.LifecycleBase.start(
	at org.apache.catalina.core.ContainerBase$
	at org.apache.catalina.core.ContainerBase$
	at java.util.concurrent.FutureTask$Sync.innerRun(
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$

Once I added the context.xml file (with just an empty <context/> element) to the project
the new plugin ran fine like the old one.

Is there something wrong with my archetype's pom (link at the top) requiring me to create
this empty context.xml file?  If not, then it looks like a bug in the plugin -- I shouldn't
be required to create an empty META-INF/context.xml file when using this plugin -- it should
be able to default to whatever defaults it is using with this empty file I'm now providing

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message