struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Woon (JIRA)" <>
Subject [jira] [Commented] (WW-4100) "error" result defined in global-results is ignored when using convention plugin
Date Tue, 11 Jun 2013 08:10:20 GMT


Mark Woon commented on WW-4100:

Sorry, I'm not following you.

My assumption is that Struts has been working this way for a long time and I don't want to
introduce something that's not backwards compatible.  Hence the new constant.

When you say "basically it's a bug as other options are overwritten" are you referring to
the constant I'm proposing?  I don't understand what option this new constant overrides.

Attaching patch now.  For future reference do you guys prefer patches in JIRA over pull requests
on GitHub?
> "error" result defined in global-results is ignored when using convention plugin
> --------------------------------------------------------------------------------
>                 Key: WW-4100
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - Convention
>    Affects Versions:
>            Reporter: Mark Woon
>            Assignee: Lukasz Lenart
>             Fix For: 2.3.16
>         Attachments: Fix_for_WW-4100_.patch
> If you have an "error" result defined in global-results in struts.xml and use the convention
plugin, the global error result is ignored.
> If you have this:
> {code}
>     <global-results>
>       <result name="error" type="dispatcher">/error/strutsError.jsp</result>
>     </global-results>
>   </package>
> {code}
> The convention plugin will only dispatch to action-error.jsp or action.jsp when the former
is not found, ignoring the global-results.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message