You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Eric Giguere <er...@videotron.ca> on 2005/02/01 16:47:00 UTC

Re: [commons-validator] I18n question

Hi

Educating indeed.
One problem is that we cannot leave out all fields from the form, it 
requires at least one entry. So we still have to declare the form and to 
copy at least one field definition.

This patch will totally remove the need to redefine all the forms from 
what I've understand. Is there a build available with this patch 
applied? I'm not really setup to build the sources...yet.
And what about the "state" of the patch, will it be included in an 
incomming release of the commons val?

thx.
Eric.

David Graham wrote:

>Comment 1 in this bug:
>http://issues.apache.org/bugzilla/show_bug.cgi?id=16920
>indicates that fields not defined in a localized formset are validated
>with the rules from the "base" formset.  So, maybe you need to declare
>each formset for each language but leave out all of the fields from the
>french set so they'll be validated by the base.
>
>HTH,
>David
>
>
>--- Eric Giguere <er...@videotron.ca> wrote:
>
>  
>
>>Hi all
>>
>>Got a small question.
>>
>>I'm trying now to add some validations in my validation.xml file that 
>>are specific to a language: French.
>>The issue I have now is that when I create a new formset with the 
>>language specified, the framework throws me an exception :
>>
>>org.apache.jasper.JasperException: No form found under 'logonForm' in 
>>locale 'fr_CA'.
>>
>>This is true, I don't have my logonForm declared in the french formset 
>>since I don't have specific rules for this one but it IS declared in the
>>
>>default formset.
>>
>>So, my question would be:
>>
>>Is it REQUIRED to redeclare every single form we see in the default 
>>formset in the new formset specific to a language?
>>
>>If so... thinking about enhancing this feature..? It doesn't make sense 
>>to redeclare everything just because you have some validations that are 
>>specific to a language. Overriding only the required fields should be 
>>enough if this engine is to work with the same "principles" than the 
>>Ressource mechanism of Java does.
>>
>>thx for the help!
>>Eric.
>>
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-user-help@jakarta.apache.org
>>
>>
>>    
>>
>
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam?  Yahoo! Mail has the best spam protection around 
>http://mail.yahoo.com 
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
>  
>


Re: [commons-validator] I18n question

Posted by David Graham <gr...@yahoo.com>.
Eric,
The bug is still open so the patch has not been applied.  Building the
source should be as simple as checking out validator from svn, cd into the
base directory, and running 'maven dist'.

David

--- Eric Giguere <er...@videotron.ca> wrote:

> Hi
> 
> Educating indeed.
> One problem is that we cannot leave out all fields from the form, it 
> requires at least one entry. So we still have to declare the form and to
> 
> copy at least one field definition.
> 
> This patch will totally remove the need to redefine all the forms from 
> what I've understand. Is there a build available with this patch 
> applied? I'm not really setup to build the sources...yet.
> And what about the "state" of the patch, will it be included in an 
> incomming release of the commons val?
> 
> thx.
> Eric.
> 
> David Graham wrote:
> 
> >Comment 1 in this bug:
> >http://issues.apache.org/bugzilla/show_bug.cgi?id=16920
> >indicates that fields not defined in a localized formset are validated
> >with the rules from the "base" formset.  So, maybe you need to declare
> >each formset for each language but leave out all of the fields from the
> >french set so they'll be validated by the base.
> >
> >HTH,
> >David
> >
> >
> >--- Eric Giguere <er...@videotron.ca> wrote:
> >
> >  
> >
> >>Hi all
> >>
> >>Got a small question.
> >>
> >>I'm trying now to add some validations in my validation.xml file that 
> >>are specific to a language: French.
> >>The issue I have now is that when I create a new formset with the 
> >>language specified, the framework throws me an exception :
> >>
> >>org.apache.jasper.JasperException: No form found under 'logonForm' in 
> >>locale 'fr_CA'.
> >>
> >>This is true, I don't have my logonForm declared in the french formset
> 
> >>since I don't have specific rules for this one but it IS declared in
> the
> >>
> >>default formset.
> >>
> >>So, my question would be:
> >>
> >>Is it REQUIRED to redeclare every single form we see in the default 
> >>formset in the new formset specific to a language?
> >>
> >>If so... thinking about enhancing this feature..? It doesn't make
> sense 
> >>to redeclare everything just because you have some validations that
> are 
> >>specific to a language. Overriding only the required fields should be 
> >>enough if this engine is to work with the same "principles" than the 
> >>Ressource mechanism of Java does.
> >>
> >>thx for the help!
> >>Eric.
> >>
> >>
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: commons-user-help@jakarta.apache.org
> >>
> >>
> >>    
> >>
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Tired of spam?  Yahoo! Mail has the best spam protection around 
> >http://mail.yahoo.com 
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: commons-user-help@jakarta.apache.org
> >
> >
> >  
> >
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org