beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlin Rogers (JIRA)" <>
Subject [jira] Assigned: (BEEHIVE-307) Struts validator support for the msg and args' bundle attribute is not working
Date Thu, 09 Jun 2005 20:31:16 GMT
     [ ]

Carlin Rogers reassigned BEEHIVE-307:

    Assign To: Rich Feit  (was: Carlin Rogers)

Assigning to Rich to consider an upgrade of NetUI to use Struts 1.2.7.
Struts bug 21760 was fixed in the Struts 1.2.x on 3/29/2005 and should be 
part of the  Struts 1.2.7 release. 

There was a Struts announcement on 5/26/2005 about the GA release
of 1.2.7. 

With the upgrade we should be able to close this bug.

> Struts validator support for the msg and args' bundle attribute is not working
> ------------------------------------------------------------------------------
>          Key: BEEHIVE-307
>          URL:
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Carlin Rogers
>     Assignee: Rich Feit
>     Priority: Minor
>      Fix For: TBD
>  Attachments: bundles-test-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...
> 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:
For more information on JIRA, see:

View raw message