NullPointerException instead of "There is no Action mapped for namespace..." 
(regression?)
------------------------------------------------------------------------------------------

                 Key: WW-3770
                 URL: https://issues.apache.org/jira/browse/WW-3770
             Project: Struts 2
          Issue Type: Bug
          Components: Core Actions
    Affects Versions: 2.3.1.2
            Reporter: Antoine W


After upgrading to Struts 2.3.1.2, we get a Nullpointer when trying to access 
an undefined action (in example, /badurl.do) - see complete stack below.
This is because ServletActionContext.getRequest() is NULL when 
getErrorMessage() gets called.
This is a major issue because it prevents 404 error to be handled correctly and 
it affects several websites (just Google for 
"org.apache.struts2.impl.StrutsActionProxy.getErrorMessage(StrutsActionProxy.java:69)")

java.lang.NullPointerException
        
org.apache.struts2.impl.StrutsActionProxy.getErrorMessage(StrutsActionProxy.java:69)
        
com.opensymphony.xwork2.DefaultActionProxy.prepare(DefaultActionProxy.java:185)
        
org.apache.struts2.impl.StrutsActionProxy.prepare(StrutsActionProxy.java:63)
        
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:500)
        
org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:434)
        
com.cardiweb.cardiboxv6.web.struts2.Struts2Filter.doFilter(Struts2Filter.java:40)
        
com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129)
        
com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
        
org.apache.struts2.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:102)



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to