[
https://issues.apache.org/struts/browse/STR-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41470
]
Paul Benedict commented on STR-3070:
------------------------------------
Because some users prefer to support S1 with Spring, it is impossible for them
to use postback forms with the custom Spring subclass of RequestProcessor. The
problem is two lines of missing code to set the request attribute. I will fix
this and back port it to 1.3.x to favor these users.
> Postback form rendering fails if ORIGINAL_URI key not present
> -------------------------------------------------------------
>
> Key: STR-3070
> URL: https://issues.apache.org/struts/browse/STR-3070
> Project: Struts 1
> Issue Type: Bug
> Components: Taglibs
> Reporter: Paul Benedict
> Assignee: Paul Benedict
> Priority: Minor
> Fix For: 1.3.10, 1.4.0
>
>
> 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.
