[jboss-dev-forums] [JBoss Web Development] - jboss-5.1.0.GA / struts-2.2.1.1 deployment inconsistency

[Mitch McKenzie]

Mitch McKenzie [http://community.jboss.org/people/mmckenzie] created the discussion

"jboss-5.1.0.GA / struts-2.2.1.1  deployment inconsistency"

To view the discussion, visit: http://community.jboss.org/message/601079#601079

--------------------------------------------------------------
If I copy the attached sample struts 2 application to C:\jboss-5.1.0.GA\server\default\deploy and hit the following url  http://localhost:8080/Struts2_Annotations_Mvn/ http://localhost:8080/Struts2_Annotations_Mvn/  everything works fine.


If I deploy the application in exploded form (C:\jboss-5.1.0.GA\server\default\deploy\Struts2_Annotations_Mvn.war\WEB-INF, META-INF, index.jsp) and hit the url:  http://localhost:8080/Struts2_Annotations_Mvn/ http://localhost:8080/Struts2_Annotations_Mvn/ the main page will load but if I click on the " http://localhost:8080/Struts2_Annotations_Mvn/hello.action Get your hello." link it does not work and I receive the following error: 

 Struts Problem Report  Struts has detected an unhandled exception: Messages:       There is no Action mapped for namespace / and action name hello. Stacktraces There is no Action mapped for namespace / and action name hello. - [unknown location]      com.opensymphony.xwork2.DefaultActionProxy.prepare(DefaultActionProxy.java:189)     org.apache.struts2.impl.StrutsActionProxy.prepare(StrutsActionProxy.java:61)     org.apache.struts2.impl.StrutsActionProxyFactory.createActionProxy(StrutsActionProxyFactory.java:39)     com.opensymphony.xwork2.DefaultActionProxyFactory.createActionProxy(DefaultActionProxyFactory.java:58)     org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:475)     org.apache.struts2.dispatcher.ng.ExecuteOperations.executeAction(ExecuteOperations.java:77)     org.apache.struts2.dispatcher.ng.filter.StrutsPrepareAndExecuteFilter.doFilter(StrutsPrepareAndExecuteFilter.java:91)     org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)     org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)     org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)     org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)     org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)     org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)     org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)     org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)     org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)     org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)     org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)     org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)     org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)     org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)     org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)     org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)     org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)     java.lang.Thread.run(Unknown Source)       You are seeing this page because development mode is enabled. Development mode, or devMode, enables extra debugging behaviors and reports to assist developers. To disable this mode, set:    struts.devMode=false  in your WEB-INF/classes/struts.properties file. 



*What is different between the two deployment methods that would cause the difference in behavior?*
--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/601079#601079]

Start a new discussion in JBoss Web Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2112]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20110420/778340f3/attachment.html