You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-issues@incubator.apache.org by "Simon Lessard (JIRA)" <ad...@incubator.apache.org> on 2006/07/06 13:10:30 UTC

[jira] Created: (ADFFACES-44) does not allow EL for noMatchMessageDetail

<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


[jira] Commented: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/ADFFACES-44?page=comments#action_12419789 ] 

Simon Lessard commented on ADFFACES-44:
---------------------------------------

Here's some precision on this bug. The expression language does not seem to be the real issue.

I ran the test again using the following code:

<f:loadBundle basename="messages" var="msg"/>
<af:inputText label="Test">
  <af:validateRegExp pattern="\w*" noMatchMessageDetail="TEST"/>
</af:inputText>

It always works. I also ran it using:

<f:loadBundle basename="messages" var="msg"/>
<af:inputText label="Test">
  <af:validateRegExp pattern="\w*" noMatchMessageDetail="TEST"/>
</af:inputText>

messages.properties :
error = This is a test message

With client validation enabled, the JavaScript message is shown correctly. However, if I disable client validation, the message detail I get under the field is the default one : 
The value "%?&" does not match the regular expression pattern "\w*".

Another note concerning i18n here. If I run the same test in French I get : 
La valeur "%?&" ne correspond pas au motif dexpression régulière "{2}".

It seems that {2} won't get parsed. I think this issue is related to ADFFACES-46 as FastMessageFormat detects the single quote that would normally be present in "d'expression" that cause the {2} to be escaped and thus not evaluated.

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


[jira] Updated: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/ADFFACES-44?page=all ]

Simon Lessard updated ADFFACES-44:
----------------------------------

    Status: Patch Available  (was: Open)

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


[jira] Commented: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/ADFFACES-44?page=comments#action_12419790 ] 

Simon Lessard commented on ADFFACES-44:
---------------------------------------

Oups, little copy and paste error here, second test was made using :

<f:loadBundle basename="messages" var="msg"/>
<af:inputText label="Test">
  <af:validateRegExp pattern="\w*" noMatchMessageDetail="#{msg['error']}"/>
</af:inputText> 


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


[jira] Commented: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Adam Winer (JIRA)" <ad...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/ADFFACES-44?page=comments#action_12420339 ] 

Adam Winer commented on ADFFACES-44:
------------------------------------

Minor comments and questions on the patch: 
 - In general, avoid reformatting files when submitting patches;  it makes
   it far more time consuming to review the patch.
 - Specifically, in:

-  public void validate(
-    FacesContext context,
-    UIComponent component,
-    Object value
-    ) throws ValidatorException
+  public void validate(FacesContext context, UIComponent component, Object value)
+                                                                                 throws ValidatorException
 
.... the old formatting is preferred.

- getNoMatchMessageDetailNoEval() does not need to be protected, so it should be
  private.  (General coding rule for Trinidad - nothing should be protected unless
  it absolutely is required by subclasses.)

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


[jira] Commented: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/ADFFACES-44?page=comments#action_12420347 ] 

Simon Lessard commented on ADFFACES-44:
---------------------------------------

Fixed patch with a version 2 using a private method and no CTRL-SHIFT-F.

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


[jira] Updated: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/ADFFACES-44?page=all ]

Simon Lessard updated ADFFACES-44:
----------------------------------

    Attachment: ValidatorEL.patch

This version of the patch fix the problem for all validators, not just validateRegExp. However, it modifies more files.

> <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, ValidatorEL.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


[jira] Updated: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
     [ 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


[jira] Commented: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/ADFFACES-44?page=comments#action_12420388 ] 

Simon Lessard commented on ADFFACES-44:
---------------------------------------

I added another patch. It's more complete and fix the issue with all validators. A version for converters as well might be still needed. I had to add a getRawProperty to FacesBean to make it as reusable as possible, the change in various validators and converters then become trivial.

> <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, ValidatorEL.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


[jira] Commented: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/ADFFACES-44?page=comments#action_12420077 ] 

Simon Lessard commented on ADFFACES-44:
---------------------------------------

Retested with revision 420024. The issue with the {2} being shown is fixed (since issue ADFFACES-46 was fixed). However, the original issue about EL not supported when client validation is disabled is still relevant.

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


[jira] Updated: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/ADFFACES-44?page=all ]

Simon Lessard updated ADFFACES-44:
----------------------------------

    Attachment:     (was: RegExpValidatorEL.patch)

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


[jira] Updated: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Matthias Weßendorf (JIRA)" <ad...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/ADFFACES-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Weßendorf updated ADFFACES-44:
---------------------------------------

        Fix Version/s: 1.0.0-incubating-core
    Affects Version/s: 1.0.0-incubating-core

> <af:validateRegExp/> does not allow EL for noMatchMessageDetail
> ---------------------------------------------------------------
>
>                 Key: ADFFACES-44
>                 URL: https://issues.apache.org/jira/browse/ADFFACES-44
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>    Affects Versions: 1.0.0-incubating-core
>            Reporter: Simon Lessard
>         Assigned To: Adam Winer
>             Fix For: 1.0.0-incubating-core
>
>         Attachments: RegExpValidatorEL.patch, ValidatorEL.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.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Adam Winer (JIRA)" <ad...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/ADFFACES-44?page=comments#action_12419802 ] 

Adam Winer commented on ADFFACES-44:
------------------------------------

Could you retest with the latest source?  (At least SVN revision 420024).  At least some of the symptoms you see here should have been fixed.

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


[jira] Commented: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
    [ 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


[jira] Updated: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Adam Winer (JIRA)" <ad...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/ADFFACES-44?page=all ]

Adam Winer updated ADFFACES-44:
-------------------------------

        Status: Resolved  (was: Patch Available)
    Resolution: Fixed

Patch checked in - thanks!

> <af:validateRegExp/> does not allow EL for noMatchMessageDetail
> ---------------------------------------------------------------
>
>                 Key: ADFFACES-44
>                 URL: http://issues.apache.org/jira/browse/ADFFACES-44
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>            Reporter: Simon Lessard
>         Assigned To: Adam Winer
>         Attachments: RegExpValidatorEL.patch, ValidatorEL.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

        

[jira] Commented: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/ADFFACES-44?page=comments#action_12420095 ] 

Simon Lessard commented on ADFFACES-44:
---------------------------------------

Follow-up on this issue. I tested with some System.out.print and here is what I get on first page rendering:

06/07/10 10:41:02 getNoMatchMessageDetail() obj = This is a test message
06/07/10 10:41:02 getNoMatchMessageDetail() obj = This is a test message

and on page submit:

06/07/10 10:41:26 getNoMatchMessageDetail() obj = null
06/07/10 10:41:26 _getNoMatchFoundMessage() = Detail: La valeur "/$%" ne correspond pas au motif d'expression régulière "\w*"., Summary: La valeur ne correspond pas au motif.
06/07/10 10:41:26 getNoMatchMessageDetail() obj = This is a test message
06/07/10 10:41:26 getNoMatchMessageDetail() obj = This is a test message

For some reason it seems that the noMatchMessageDetail attribute is not yet restored during the processValidation phase, but get restored just fine during render response. I'll dig that one a bit more.

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


[jira] Updated: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Simon Lessard (JIRA)" <ad...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/ADFFACES-44?page=all ]

Simon Lessard updated ADFFACES-44:
----------------------------------

    Attachment: RegExpValidatorEL.patch

Version 2 with private method and no CTRL-SHIFT-F compulsion :)

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


[jira] Assigned: (ADFFACES-44) does not allow EL for noMatchMessageDetail

Posted by "Adam Winer (JIRA)" <ad...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/ADFFACES-44?page=all ]

Adam Winer reassigned ADFFACES-44:
----------------------------------

    Assignee: Adam Winer

> <af:validateRegExp/> does not allow EL for noMatchMessageDetail
> ---------------------------------------------------------------
>
>                 Key: ADFFACES-44
>                 URL: http://issues.apache.org/jira/browse/ADFFACES-44
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>            Reporter: Simon Lessard
>         Assigned To: Adam Winer
>         Attachments: RegExpValidatorEL.patch, ValidatorEL.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