[
https://issues.apache.org/jira/browse/TOMAHAWK-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556604#action_12556604
]
Todd Gould commented on TOMAHAWK-1104:
--------------------------------------
Simon,
Thanks for your input on this issue. I suspect you 'wild guess' is dead on.
Our pages are a composition of multiple collaborating webapps concurrently
displayed on the same browser screen (enabled via extensive use of
AjaxAnywhere). Therefore, there are always multiple forms on the screen at the
same time. Are you aware of anyway that we could either 1) ensure that the
"enter" button triggers the form associated to the one the control is declared
in or 2) ensure that the inputDate data does get posted?
TIA!
> <t:inputCalendar> does not completely recover from submitted date/time
> formatting/validation errors
> ---------------------------------------------------------------------------------------------------
>
> Key: TOMAHAWK-1104
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1104
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Calendar
> Affects Versions: 1.1.6
> Environment: Windows XP, IE 6, MyFaces 1.1.5, Tomahawk 1.1.6
> Reporter: Todd Gould
> Attachments: HtmlCalendarRenderer.java
>
>
> There appears to be a problem with the <t:inutCalendar> component recovering
> from user entry errors. For example, if I am using the following tag in a
> JSP:
> <t:inputCalendar id="SinceAlertTime"
> value="#{alertSummaryController.sinceTime}"
> popupDateFormat="MM/dd/yyyy HH:mm:ss" helpText="MM/dd/yyyy
> HH:mm:ss"
> title="MM/dd/yyyy HH:mm:ss"
> popupSelectDateMessage="Select [date] as date"
> renderAsPopup="true" renderPopupButtonAsImage="true">
> All works as desired unless the user manually enters an invalid date/time
> format (for example a typo) in the associated text entry field generated by
> this component. In this case the scenario is as follows:
> 1. The user inadvertently enters a bad date/time format into the associated
> text entry field and subsequently submits the form.
> 2. The validation error is correctly created and displayed back to the user
> (validation failed, so Invoke Application phase never performed).
> 3. The user then corrects their error by either manually entering a valid
> format in the associated text entry field or by invoking the popup and
> selecting a date.
> 4. The user then submits the form and the now corrected date is apparently
> accepted (i.e. no validation error). However, the previously invalid value
> is retained as the backing bean is not set and the resulting text entry field
> displayed contains the user entered invalid date/time format upon redisplay.
> We are using CLIENT state saving method as our ajax implementation relies
> upon this. I have not had a chance to see if that matters or not, but submit
> it for complete information.
> This is a severe problem for us as our user community frequently uses both
> the popup to select a date and then subsequently manually adjusts the time
> portion in the text entry field. If they inadvertantly create an invalid
> entry in this fashion, they are basically stuck as the component does not
> appear to recover upon re-submission of valid date/time values in the
> associated text entry field - i.e. the error keeps re-appearing upon
> subsequent submissions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
