[ http://issues.apache.org/jira/browse/BEEHIVE-307?page=all ]
Carlin Rogers updated BEEHIVE-307:
----------------------------------
Attachment: j307-patch.txt
The following patch includes a fix to the ErrorbaseTag.getErrorMessage() method
to check if
the error ActionMessage is a resource or not. If not, then we just get the
already formatted
message and return. This fix is in place because the struts validator Resources
class will
format the message using the alternate resource bundle and create the new
ActionMessage
with resource=false.
The patch also has the updated test files along with a new testRecorder BVT.
> Struts validator support for the msg and args' bundle attribute is not working
> ------------------------------------------------------------------------------
>
> Key: BEEHIVE-307
> URL: http://issues.apache.org/jira/browse/BEEHIVE-307
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Reporter: Carlin Rogers
> Assignee: Carlin Rogers
> Priority: Minor
> Fix For: TBD
> Attachments: bundles-test-patch.txt, j307-patch.txt
>
> Struts does not correctly get validator msg and args from alternate resource
> bundles. Struts ignores a bundle attribute defined in the validation XML msg
> or args element tags used in the commons-validator framework.
> There's already a bug in struts on this. Here's a summary,
> Bug 21760 already includes a patch to go into Struts to resolve this issue.
> The patch is dependent on some changes in Commons Validator that are part of
> Validator 1.1.4. Struts is waiting for a "GA" quality release of Validator
> 1.1.4, then will move the Struts dependency to 1.1.4 and apply the fix.
> and the details...
> http://issues.apache.org/bugzilla/show_bug.cgi?id=21760
> Unfortunately this implies that the NetUI annotations for validator msg and
> args alternate resource bundles will not work until the fix in struts is
> integrated into NetUI. User will need to keep msg and args in the default
> resource bundle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
