You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Niall Pemberton (JIRA)" <ji...@apache.org> on 2006/05/07 12:03:52 UTC
[jira] Commented: (STR-2795) Postback Forms - Caching and Modules
[ http://issues.apache.org/struts/browse/STR-2795?page=comments#action_37305 ]
Niall Pemberton commented on STR-2795:
--------------------------------------
The problem is not with container pooling, but in the way that "postback forms" have been implemented in this tag - the way the tag's "action" attribute is modified is incorrect.
On the issue of the modules - it will only ever be the current module - so iterating through other modules would not be necessary.
Closing this is a mistake IMO - the only way this issue is not going to bite people is if the "postback forms" feature is never used.
> Postback Forms - Caching and Modules
> ------------------------------------
>
> Key: STR-2795
> URL: http://issues.apache.org/struts/browse/STR-2795
> Project: Struts Action 1
> Type: Bug
> Components: Taglibs
> Versions: Nightly Build
> Environment: Operating System: other
> Platform: Other
> Reporter: Niall Pemberton
> Assignee: Don Brown
>
> I experimented with a postback form in the struts-examples exercise modules and
> found two problems:
> 1) Postback forms take no account of modules so when the FormTag lookup()
> method calls TagUtils.getActionMappingName() it doesn't find the action.
> 2) More seriously, postback forms don't take into account the fact that servlet
> containers cache Tags. The way "postback" has been implemented, by setting
> the "action" attribute, is not going to work properly when the FormTag is
> cached and re-used on a different form.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira