[forge-issues] [JBoss JIRA] (FORGE-460) RichFaces date picker is not used when RichFaces is used on a @Temporal(TIMESTAMP) Date field

[Richard Kennard (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663916#comment-12663916 ] 

Richard Kennard commented on FORGE-460:
---------------------------------------

Emmanuel,

I agree most validations won't apply to search fields. I think an 'easy default' (i.e. without requiring people to modify their domain model) would be to just add <f:validateBean disabled="#{true}"/> to each search field.

However this doesn't appear to survive POST-back (i.e. it works for one click, but then fails after that). Are you aware of this? Is it a bug? I attach a minimal test case. I'd be most grateful if you could look at it.

If you agree it is a bug, could you raise it with the relevant team? I could do it myself, but you have the whole 'scary French genius' thing going on so can probably get people to react more quickly :)

Regards,

Richard.
                
> RichFaces date picker is not used when RichFaces is used on a @Temporal(TIMESTAMP) Date field 
> ----------------------------------------------------------------------------------------------
>
>                 Key: FORGE-460
>                 URL: https://issues.jboss.org/browse/FORGE-460
>             Project: Forge
>          Issue Type: Feature Request
>          Components: Scaffold
>            Reporter: Pete Muir
>            Assignee: Richard Kennard
>             Fix For: Future
>
>         Attachments: datepicker.tiff, emmanuel.zip
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira