[ http://issues.apache.org/struts/browse/STR-2795?page=all ]
Don Brown resolved STR-2795:
----------------------------
Resolution: Cannot Reproduce
As to your points:
1) True, but I don't see any way around this. Sure, we could check for the
current module, but otherwise, we'd have to iterate through all the modules to
detect another one, and that isn't feasible I don't think
2) Well, if the container doesn't pool properly, that is out of our control,
and more tags than this one will have problems.
I'm resolving this as I can't reproduce the issue, but please reopen if you can
think of ways we can write this more defensively.
> 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
