[
https://issues.jboss.org/browse/FORGE-913?page=com.atlassian.jira.plugin....
]
Vineet Reynolds updated FORGE-913:
----------------------------------
Status: Closed (was: Pull Request Sent)
Resolution: Done
Pushed upstream :
https://github.com/forge/core/commit/bad139e68befddf1d1f30286978a746a7c16...
RichFaces calendar components are now created with a datePattern attribute that contains
time attributes. This results in a time picker made available during input of timestamps.
It should be noted that the apply button is not shown, and hence the time is defaulted,
but modifiable.
RichFaces scaffolding does not handle temporal fields in JPA entities
correctly
-------------------------------------------------------------------------------
Key: FORGE-913
URL:
https://issues.jboss.org/browse/FORGE-913
Project: Forge
Issue Type: Bug
Components: Scaffold
Affects Versions: 1.0.5.Final, 1.3.0.Final
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Fix For: 1.x Future
The RichFaces scaffold generator creates {{rich:calendar}} components in the facelets,
but without a {{datePattern}} attribute. The behavior of this component in such a case is
to not provide the embeddded timepicker. This works for temporal fields of type Date.
But, this is certainly not sufficient for temporal fields of type Timestamp. A
{{datePattern}} with a time pattern like {{MMM d, yyyy HH:mm}} or {{MMM d, yyyy hh:mm:a}}
needs to be generated for such fields to allow time inputs.
For temporal fields of type Time, consider generating a different widget, since the
RichFaces calendar widget is not capable of providing the timepicker alone.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira