[
https://issues.jboss.org/browse/FORGE-460?page=com.atlassian.jira.plugin....
]
Richard Kennard edited comment on FORGE-460 at 1/31/12 9:07 PM:
----------------------------------------------------------------
Further fixes for: CSS fixes. Adding multiple one-to-many at once. Required field
handling. Nested collections.
Note we appear to have a bit of an issue with Bean Validation's @NotEmpty. Pete could
you please investigate? Basically:
1. Generate the app
2. Cheer how the date pickers no longer overlap
3. Cry because when you go 'Booking->Create New' you get validation errors on
the search fields
Now, I have already removed JSF's 'required=true' attribute from these fields.
So it appears it is Bean Validation doing this. You cannot use 'immediate=true' on
the button or else nothing will get POSTed at all.
The 'correct' solution, I think, is to add f:validateBean
disabled="true" to each of the required fields. I can do this no problem, but it
doesn't seem to work (under AS 7.0.2.Final).
Example:
1. Add 'f:validateBean disabled=true' to 'h:inputText
id="bookingBeanSearchCancellationCode"' and 'h:inputText
id="bookingBeanSearchContactEmail"' in 'booking/search.xhtml'
2. Go to the search screen and click 'Create New'. Works! Hurrah!
3. Go back to the search screen and click 'Search' and then 'Create New'.
Now it fails. It appears f:validateBean does not survive POST-back? Is this a bug?
Even if this *did* work, a bad side effect is that all validation is disabled for these
fields. So for example it no longer validates the e-mail address format. We can probably
live with that on the search screens, but it may be unacceptable on the one-to-many
'add' fields (where this is also a problem).
Suggestions?
was (Author: kennardconsulting):
Further fixes for: CSS fixes. Adding multiple one-to-many at once. Required field
handling. Nested collections.
Note we appear to have a bit of an issue with Bean Validation's @NotEmpty. Pete could
you please investigate? Basically:
1. Generate the app
2. Cheer how the date pickers no longer overlap
3. Cry because when you go 'Booking->Create New' you get validation errors on
the search fields
Now, I have already removed JSF's 'required=true' attribute from these fields.
So it appears it is Bean Validation doing this. You cannot use 'immediate=true' on
the button or else nothing will get POSTed at all.
The 'correct' solution, I think, is to add f:validateBean
disabled="true" to each of the required fields. I can do this no problem, but it
doesn't seem to work.
Example:
1. Add 'f:validateBean disabled=true' to 'h:inputText
id="bookingBeanSearchCancellationCode"' and 'h:inputText
id="bookingBeanSearchContactEmail"' in 'booking/search.xhtml'
2. Go to the search screen and click 'Create New'. Works! Hurrah!
3. Go back to the search screen and click 'Search' and then 'Create New'.
Now it fails. It appears f:validateBean does not survive POST-back? Is this a bug?
Even if this *did* work, a bad side effect is that all validation is disabled for these
fields. So for example it no longer validates the e-mail address format. We can probably
live with that on the search screens, but it may be unacceptable on the one-to-many
'add' fields (where this is also a problem).
Suggestions?
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: 1.0.0.CR1
Attachments: datepicker.tiff
--
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