[ http://issues.apache.org/jira/browse/ADFFACES-44?page=all ]
Simon Lessard updated ADFFACES-44:
----------------------------------
Attachment: RegExpValidatorEL.patch
This patch affect the following files:
org.apache.myfaces.adf.validator.RegExpValidator
// Added protected Object getNoMatchMessageDetailNoEval()
// Renamed public String getNoMatchMessageDetatil() to public String
getNoMatchMessageDetail()
org.apache.myfaces.adf.util.MessageFactory
// Modified public String getDetailMessage() of CustomDetailErrorMessage class
to prevent NullPointerException in ValidatorException constructor and
IllegalArgumentException in FastMessageFormat
org.apache.myfaces.adfinternal.validator.RegExpValidator
// Modified to use public String getNoMatchMessageDetail() instead of public
String getNoMatchMessageDetatil()
> <af:validateRegExp/> does not allow EL for noMatchMessageDetail
> ---------------------------------------------------------------
>
> Key: ADFFACES-44
> URL: http://issues.apache.org/jira/browse/ADFFACES-44
> Project: MyFaces ADF-Faces
> Type: Bug
> Reporter: Simon Lessard
> Attachments: RegExpValidatorEL.patch
>
> I copied this bug from OTN at
> http://forums.oracle.com/forums/message.jspa?messageID=1355472#1355472
> You cannot specify a noMatchMessageDetail using EL pointing on a resource
> file when using the <af:validateRegExp/> tag.
> The reproduction case is:
> [code]
> <f:loadBundle basename="some.resource.file" var="res"/>
> <af:inputText>
> <af:validateRegExp pattern="\w*"
> noMatchMessageDetail="#{res['some.key']]}"/>
> </af:inputText>
> [/code]
--
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
