You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Kris Coolsaet (JIRA)" <ji...@apache.org> on 2007/08/18 10:20:34 UTC
[jira] Created: (WW-2120) Dispatcher does not put request
parameters of new url on the value stack.
Dispatcher does not put request parameters of new url on the value stack.
-------------------------------------------------------------------------
Key: WW-2120
URL: https://issues.apache.org/struts/browse/WW-2120
Project: Struts 2
Issue Type: Bug
Components: Dispatch
Affects Versions: 2.0.9
Reporter: Kris Coolsaet
Priority: Minor
If an action dispatches to a JSP page with a query string, the parameters of that string are not available to
the page, at least not with the #parameter notation. They are when using plain JSP.
For example, consider the following action definition
<action name="DoChangePassword" class="...">
<result name="error">
<param name="location">WrongPassword.jsp?back=ChangePassword</param>
</result>
</action>
then WrongPassword.jsp has no access to #parameters.back or #parameters['back'], although the following
JSP-expression does work
<%= request.getParameter("back"))%>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WW-2120) Dispatcher does not put request
parameters of new url on the value stack.
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Holmes updated WW-2120:
-----------------------------
Fix Version/s: (was: 2.0.11)
2.0.12
> Dispatcher does not put request parameters of new url on the value stack.
> -------------------------------------------------------------------------
>
> Key: WW-2120
> URL: https://issues.apache.org/struts/browse/WW-2120
> Project: Struts 2
> Issue Type: Bug
> Components: Dispatch
> Affects Versions: 2.0.9
> Reporter: Kris Coolsaet
> Priority: Minor
> Fix For: 2.0.12
>
>
> If an action dispatches to a JSP page with a query string, the parameters of that string are not available to
> the page, at least not with the #parameter notation. They are when using plain JSP.
> For example, consider the following action definition
> <action name="DoChangePassword" class="...">
> <result name="error">
> <param name="location">WrongPassword.jsp?back=ChangePassword</param>
> </result>
> </action>
> then WrongPassword.jsp has no access to #parameters.back or #parameters['back'], although the following
> JSP-expression does work
> <%= request.getParameter("back"))%>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2120) Dispatcher does not put request
parameters of new url on the value stack.
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43917#action_43917 ]
Musachy Barroso commented on WW-2120:
-------------------------------------
This happens because #parameters is set on Dispatcher, which is not invoked when a forward, or include is made
> Dispatcher does not put request parameters of new url on the value stack.
> -------------------------------------------------------------------------
>
> Key: WW-2120
> URL: https://issues.apache.org/struts/browse/WW-2120
> Project: Struts 2
> Issue Type: Bug
> Components: Dispatch Filter
> Affects Versions: 2.0.9
> Reporter: Kris Coolsaet
> Priority: Minor
> Fix For: 2.1.3
>
>
> If an action dispatches to a JSP page with a query string, the parameters of that string are not available to
> the page, at least not with the #parameter notation. They are when using plain JSP.
> For example, consider the following action definition
> <action name="DoChangePassword" class="...">
> <result name="error">
> <param name="location">WrongPassword.jsp?back=ChangePassword</param>
> </result>
> </action>
> then WrongPassword.jsp has no access to #parameters.back or #parameters['back'], although the following
> JSP-expression does work
> <%= request.getParameter("back"))%>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WW-2120) Dispatcher does not put request
parameters of new url on the value stack.
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Musachy Barroso resolved WW-2120.
---------------------------------
Resolution: Fixed
> Dispatcher does not put request parameters of new url on the value stack.
> -------------------------------------------------------------------------
>
> Key: WW-2120
> URL: https://issues.apache.org/struts/browse/WW-2120
> Project: Struts 2
> Issue Type: Bug
> Components: Dispatch Filter
> Affects Versions: 2.0.9
> Reporter: Kris Coolsaet
> Priority: Minor
> Fix For: 2.1.3
>
>
> If an action dispatches to a JSP page with a query string, the parameters of that string are not available to
> the page, at least not with the #parameter notation. They are when using plain JSP.
> For example, consider the following action definition
> <action name="DoChangePassword" class="...">
> <result name="error">
> <param name="location">WrongPassword.jsp?back=ChangePassword</param>
> </result>
> </action>
> then WrongPassword.jsp has no access to #parameters.back or #parameters['back'], although the following
> JSP-expression does work
> <%= request.getParameter("back"))%>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2120) Dispatcher does not put request
parameters of new url on the value stack.
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43922#action_43922 ]
Musachy Barroso commented on WW-2120:
-------------------------------------
ServletDispatcherResult was modified to fix this.
> Dispatcher does not put request parameters of new url on the value stack.
> -------------------------------------------------------------------------
>
> Key: WW-2120
> URL: https://issues.apache.org/struts/browse/WW-2120
> Project: Struts 2
> Issue Type: Bug
> Components: Dispatch Filter
> Affects Versions: 2.0.9
> Reporter: Kris Coolsaet
> Priority: Minor
> Fix For: 2.1.3
>
>
> If an action dispatches to a JSP page with a query string, the parameters of that string are not available to
> the page, at least not with the #parameter notation. They are when using plain JSP.
> For example, consider the following action definition
> <action name="DoChangePassword" class="...">
> <result name="error">
> <param name="location">WrongPassword.jsp?back=ChangePassword</param>
> </result>
> </action>
> then WrongPassword.jsp has no access to #parameters.back or #parameters['back'], although the following
> JSP-expression does work
> <%= request.getParameter("back"))%>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WW-2120) Dispatcher does not put request
parameters of new url on the value stack.
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Holmes updated WW-2120:
-----------------------------
Fix Version/s: 2.0.11
> Dispatcher does not put request parameters of new url on the value stack.
> -------------------------------------------------------------------------
>
> Key: WW-2120
> URL: https://issues.apache.org/struts/browse/WW-2120
> Project: Struts 2
> Issue Type: Bug
> Components: Dispatch
> Affects Versions: 2.0.9
> Reporter: Kris Coolsaet
> Priority: Minor
> Fix For: 2.0.11
>
>
> If an action dispatches to a JSP page with a query string, the parameters of that string are not available to
> the page, at least not with the #parameter notation. They are when using plain JSP.
> For example, consider the following action definition
> <action name="DoChangePassword" class="...">
> <result name="error">
> <param name="location">WrongPassword.jsp?back=ChangePassword</param>
> </result>
> </action>
> then WrongPassword.jsp has no access to #parameters.back or #parameters['back'], although the following
> JSP-expression does work
> <%= request.getParameter("back"))%>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.