[
https://issues.jboss.org/browse/FORGE-913?page=com.atlassian.jira.plugin....
]
Vineet Reynolds updated FORGE-913:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
https://github.com/forge/core/pull/325
This adds support for supplying timestamps via the generated scaffold, with a minor
disadvantage - the time is defaulted to 12:00PM, but can be modified again. Fixing this
requires adding support in Metawidget to display the 'apply' button.
Additionally, this still does not support the input of time fields, since Richfaces
calendar does not support this component yet.
These two issues can be spun out into separate items in JIRA.
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