You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Paul Benedict (JIRA)" <ji...@apache.org> on 2007/08/18 02:48:34 UTC

[jira] Updated: (STR-3070) Postback forms cause NPE with classic RequestProcessor

     [ https://issues.apache.org/struts/browse/STR-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Benedict updated STR-3070:
-------------------------------

    Fix Version/s:     (was: 1.4.0)

> Postback forms cause NPE with classic RequestProcessor
> ------------------------------------------------------
>
>                 Key: STR-3070
>                 URL: https://issues.apache.org/struts/browse/STR-3070
>             Project: Struts 1
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.3.5, 1.3.8, 1.3.9
>            Reporter: Paul Benedict
>            Assignee: Paul Benedict
>            Priority: Critical
>             Fix For: 1.3.10
>
>
> I was unwittingly using the classic RequestProcessor when attempting to use postback forms. Unfortunately, I got a NPE:
> java.lang.NullPointerException
> 	org.apache.struts.taglib.TagUtils.getActionMappingName(TagUtils.java:583)
> 	org.apache.struts.taglib.html.FormTag.lookup(FormTag.java:834)
> 	org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:467)
> I traced the problem back to a missing step in the classic RP. It does not set the ORIGINAL_URI key like the ComposableRequestProcessor. However, FormTag should explain this condition when a postback form is used but the key is absent.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.