[ http://issues.apache.org/jira/browse/ADFFACES-44?page=comments#action_12420127 ]
Simon Lessard commented on ADFFACES-44: --------------------------------------- Yet another follow-up. I fully tracked this bug and I think it affects much more than just validateRegExp. Here's the real issue. ValueBinding does work with the tag, what won't work is a binding pointing on a bean created by another tag. For instance, in my test case, the resource bean was loaded by <f:loadBundle basename="messages" var="msg"/> and thus, at processValidation phase, the msg bean was not existing yet making the getNoMatchMessageDetail() method returns null. I could prove that creating a managed bean in faces-config.xml and have the EL point on it instead. I assume all error message attributes will react the same way. > <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 > > 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
