[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1262) Should be able to customize Hibernate validation messages based on context (by page, or role like Seam component scopes)

[Pete Muir (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-1262?page=comments#action_12360773 ] 
            
Pete Muir commented on JBSEAM-1262:
-----------------------------------

Yes, I think we definitely want to have this on the presentation layer.

Given

public class Model {

   @Length(min=10, message="#{messages.generalFooMessage}")
   private String foo;
  
   @Length(min=10, message="#{messages.generalBarMessage}")
   private String bar;

}

then

<s:validateAll>
   <h:inputText value="#{model.foo}" />
   <h:inputText value="#{model.bar}">
       <s:validate message="#{messages.specificBarMessage}" />
   </h:inputText>
</s:validateAll>

would result in foo using the message specified on the validator, and bar taking a more specific message from the nested s:validate

It could be good to have something like

<s:validateAll bundle="messageBundleForThisSetOfFields">
   ...
</s:validateAll>

similar to how you can specify a message bundle for a page.

> Should be able to customize Hibernate validation messages based on context (by page, or role like Seam component scopes)
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-1262
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1262
>             Project: JBoss Seam
>          Issue Type: Feature Request
>    Affects Versions: 1.2.1.GA
>            Reporter: Nathaniel Stoddard
>
> Currently, each validation specified a single message resource to be used as the error message.  It would be helpful if there was some way to customize the error messages to be used such that in one case "Contact address is required." is displayed, while in others "Billing address is required", for example.  Annotating model classes with validation rules limits the reuse of those classes since the validation messages offer limited flexibility.
> Since validated fields in the domain classes aren't necessarily associated with a UIInput on a page, it would be helpful to have more flexible annotations, such as:
> @MaxLength(messages = {@Message(role='contactForm', value='contact.too_long'), @Message(role='billingForm', value='billing.too_long')})
> private String field;
> Also needed would be some way of indicated to the UIView which 'role' should be used when validation takes place.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira