OK, this would be a good excuse for me to get more involved. ;-)

- Brendan

-----Original Message-----
From: Martin Marinschek (JIRA) [mailto:[EMAIL PROTECTED]

Sent: Wednesday, September 07, 2005 3:21 PM
To: [email protected]
Subject: [jira] Commented: (MYFACES-533) Optionally use a field's title
attribute as its identifier in <t:messages>


    [
http://issues.apache.org/jira/browse/MYFACES-533?page=comments#action_12
322874 ] 

Martin Marinschek commented on MYFACES-533:
-------------------------------------------

Good idea!

fancy providing a patch for this?

regards,

Martin

> Optionally use a field's title attribute as its identifier in
<t:messages>
>
------------------------------------------------------------------------
--
>
>          Key: MYFACES-533
>          URL: http://issues.apache.org/jira/browse/MYFACES-533
>      Project: MyFaces
>         Type: Improvement
>   Components: Tomahawk
>     Versions: Nightly Build
>  Environment: Any
>     Reporter: Brendan Conner
>     Priority: Minor

>
> Currently, <t:messages> inserts the offending fields' names in the
standard validation messages.  Unlike <h:messages>, it uses the text of
the field's associated outputLabel, if present, to represent the field's
name.  This is an improvement over the standard implementation, which
uses the value of the field's id attribute.  However, there are times in
which it is inconvenient to use the outputLabel.  In particular, most
outputLabels include a colon character that one wouldn't want inside the
error message.
> I would like to be able to specify that the value of the field's title
attribute be the value inserted into the standard validation error
messages, and, only if the title attribute is not present, to use the
outputLabel (or id attribute).

-- 
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

Reply via email to