[
https://issues.apache.org/jira/browse/MTOMCAT-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551113#comment-13551113
]
Glen Mazza commented on MTOMCAT-73:
-----------------------------------
That's the old Codehaus plugin ('course, this JIRA is from 2010 so that's
understandable.) A patch was provided yesterday to MTOMCAT-119 (a somewhat
related matter) with the Apache Maven Tomcat 7 plugin, and as I understand it
worked already with the tomcat6 plugin. Providing you place the context file
where it should be, i.e., src/main/webapp/META-INF/context.xml
(http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Defining_a_context),
you shouldn't need to configure this property at all.
Offhand, your use of double-slashes:
<contextFile>//META-INF/tomcat//context.xml</contextFile>, seems strange, I'm
not accustomed to that, I don't know if that's a Windows thing or something
else.
Please upgrade to the Apache Tomcat plugins and try again:
http://tomcat.apache.org/maven-plugin-2.1-SNAPSHOT/tomcat7-maven-plugin/index.html
> deploy-only goal with exliplicit contextFile-Param set leads to
> FileNotFoundException
> -------------------------------------------------------------------------------------
>
> Key: MTOMCAT-73
> URL: https://issues.apache.org/jira/browse/MTOMCAT-73
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: Maven (client): Windows XP (32bit)
> Server: Linux (Suse)
> Tomcat: 6.0.26
> Reporter: Niels Kausche
>
> Deploying a context.xml as contextFile-Parameter leads to a
> FileNotFoundException either on the client (maven command line) or on the
> server (catalina.out).
> Always with the same filename. Ist the given context.xml-File transferred to
> the server or just the file name?
> Hier is my Plugin-Configuration:
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>tomcat-maven-plugin</artifactId>
> <version>1.1</version>
> <configuration>
> <url></url>
> <path>/</path>
> <mode>context</mode>
> <contextFile>//META-INF/tomcat//context.xml</contextFile>
> </configuration>
> </plugin>
> I am using the task to deploy to our development, test, or production server
> using different jndi configurations in different context.xml files.
> Here the server stack trace (catalina.out):
> (you see, it is the original local file name from the build server. And it is
> correct.)
> java.io.FileNotFoundException:
> /C:/Entwicklung/projekte-rivotool/dr.servicecockpit.rivo.web/target/dr.servicecockpit.rivo.web-1.2.19/META-INF/tomcat/etest/
> ccontext.xml (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:106)
> at
> org.apache.catalina.manager.ManagerServlet.copyInternal(ManagerServlet.java:1671)
> at
> org.apache.catalina.manager.ManagerServlet.copy(ManagerServlet.java:1632)
> at
> org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:836)
> at
> org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:351)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:558)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
> at
> org.apache.coyote.http11.Http11ProtocolHttp11ConnectionHandler.process(Http11Protocol.java:588)
> at
> org.apache.tomcat.util.net.JIoEndpointWorker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:619)
> Exception in thread "net.sf.ehcache.CacheManager@647fc8b2"
> java.lang.NullPointerException
> at
> org.slf4j.impl.Log4jLoggerAdapter.debug(Log4jLoggerAdapter.java:204)
> at
> net.sf.ehcache.util.UpdateChecker.checkForUpdate(UpdateChecker.java:62)
> at net.sf.ehcache.util.UpdateChecker.run(UpdateChecker.java:50)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
--
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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
