Timezone included in af:inputDate causes IllegalArgumentException (Doc ID 1600944.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle JDeveloper - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

An af:inputDate who’s value is bound to a data control has a custom validator. The inputDate also contains an “af:convertDateTime” child that has “dd-MMM-yyyy k:mm z” as its “pattern” attribute.

Problems:
1: If the component is bound to the data control, validators on the component receive a “String” object instead of a date object. This String does not include the time zone attribute. Instead, it only returns the text that is displayed in the text box part of the inputDate component.

2: When a “min value” is set on the inputDate object, an error is received stating it cannot convert a String to a Date. The string specified is the same string that is passed to the custom validator.

3: If the “min value” is removed, the following error is shown when the component’s data is submitted:


4: If the “z” part of the convertDateTime pattern is removed, problems 2 and 3 are not seen. However, the time zone specified s then determined by the server’s locale and not based on the client’s locale, so the ability for the user to select their timezone is lost.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms