Re: Validator 1.0 Release and bug 10868

[Joe Germuska]

At 7:56 PM -0400 2002/10/16, James Turner wrote:

At 07:31 PM 10/16/2002, Craig R. McClanahan wrote:

 > One bug under Struts that should really be addressed in the base code is

 the question of specifying alternate resource bundles forms and fields (bug
 #10868).  As I understand it, this will cause problems for Validator with
 sub-apps under Struts.  Should I try to tackle it?

Please do!

Ok, but I can't think of a clean way to handle it.

Here's the issue:

The base Validator doesn't deal with resource bundles (or errors messages for that matter) at all. It's the validator Framework that does all that stuff. So putting bundle= support into the base Validator DTD for forms isn't very clean, since it required putting Struts-specific stuff into the Validator DTD (and adding a bundle property to the Field class)

Any thoughts on how we can implement this in a way that keeps Validator Struts-neutral?

How about this: extend the Validator API to allow users to set an instance of "org.apache.commons.resources.ResourcesManager" Then in Struts, finish adapting it to use commons-resources (which is just factored out of Struts, so probably wouldn't be too difficult). Then in the StrutsValidatorPlugin, have the plugin pass the ResourcesManager to the validator.

The problem being that Struts hasn't really switched over to commons-resources yet. That would end up touching almost every class! Who wants to take that on when the masses are clamoring at the gates for a 1.1 final release!

Joe

--
--
* Joe Germuska { [EMAIL PROTECTED] }
"It's pitiful, sometimes, if they've got it bad. Their eyes get glazed, they go white, their hands tremble.... As I watch them I often feel that a dope peddler is a gentleman compared with the man who sells records."
--Sam Goody, 1956

--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>