[
https://issues.apache.org/jira/browse/MTOMCAT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795318#comment-13795318
]
Neale Upstone commented on MTOMCAT-243:
---------------------------------------
The above log traces indicate that the WAR is at the very least getting scanned
by the Tomcat container, at which point I would expect there to be no
difference between running from a WAR project and running with <webapps>. A
bit baffled, but will investigate further.
> Tomcat7 deploys, but doesn't start apps defined in <webapps>
> ------------------------------------------------------------
>
> Key: MTOMCAT-243
> URL: https://issues.apache.org/jira/browse/MTOMCAT-243
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Reporter: Neale Upstone
>
> Using the same <webapps> config as with the tomcat6 plugin, I'm getting the
> following with Tomcat 7:
> [INFO] Deploying dependency wars
> [INFO] Deploy warfile:
> /home/neale/.m2/repository/blah/blah-war-1.0.0.CI-SNAPSHOT.war to
> contextPath: /blah-war
> Oct 15, 2013 2:28:53 PM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["http-bio-8082"]
> Oct 15, 2013 2:28:53 PM org.apache.catalina.core.StandardService startInternal
> INFO: Starting service Tomcat
> Oct 15, 2013 2:28:59 PM org.apache.catalina.core.ApplicationContext log
> INFO: No Spring WebApplicationInitializer types detected on classpath
> Oct 15, 2013 2:28:59 PM org.apache.coyote.AbstractProtocol start
> Yet this works if I run from the WAR project using run-war.
> The "No Spring WebApplicationInitializer" initially caught my eye, but is
> actually the default informational message emitted when run in a 3.0
> container.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
