You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Neale Upstone (JIRA)" <ji...@apache.org> on 2013/10/15 17:12:41 UTC
[jira] [Updated] (MTOMCAT-243) Tomcat7 deploys, but doesn't start
webapp 2.5 apps defined in
[ https://issues.apache.org/jira/browse/MTOMCAT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neale Upstone updated MTOMCAT-243:
----------------------------------
Description:
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.
was:
Using the same <webapps> config as with the tomcat6 plugin, I'm getting the following with Tomcat 7:
{noformat}
[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
{noformat}
Yet this works if I run from the WAR project using run-war.
The "No Spring WebApplicationInitializer" log message would seem to indicate that the WAR is being treated as a 3.0 version webapp and calling the Spring entry point.
> Tomcat7 deploys, but doesn't start webapp 2.5 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org