<af:validateDateTimeRange>

This validator provides hints for the help framework, which cannot be turned off.

This validator also runs on the client (implements org.apache.myfaces.trinidad.validator.ClientValidator).

Attributes

Name

Type

Supports EL?

Description

hintMaximum

String

Yes

Hint message to be used, to give a hint about the allowed maximum.

Parameters:

{0} the maximum

hintMinimum

String

Yes

Hint message to be used, to give a hint about the allowed minimum.

Parameters:

{0} the minimum

hintNotInRange

String

Yes

Hint message to be used, to give a hint about the allowed range.

Parameters:

{0} the minimum

{1} the maximum

maximum

java.util.Date

Yes

the maximum java.util.Date. ISO 8601 date strings, of the form 'yyyy-MM-dd' (for example 2004-06-22) is also allowed - the created Date object will be in the application's timezone with the time components (hours, minutes, seconds, milliseconds) maximized. This will be parsed to date. When binding to Date objects, it is advised to create the Date object with maximum value for any date-time components that aren't displayed (usually hours, minutes, seconds, milliseconds) to allow the largest range of values to be accepted.

messageDetailMaximum

String

Yes

The detail error message to be used for constructing faces messages, when input value exceeds the maximum value set.

Parameters:

{0} the label that identifies the component

{1} value entered by the user

{2} the maximum allowed date

Please note: Parameter {1} which specifies the value entered by the user, should never be used in the message if the value is secure, like when secret=true on inputText.

messageDetailMinimum

String

Yes

The detail error message to be used for constructing faces messages, when input value is less than the set minimum value.

Parameters:

{0} the label that identifies the component

{1} value entered by the user

{2} the minimum allowed date

Please note: Parameter {1} which specifies the value entered by the user, should never be used in the message if the value is secure, like when secret=true on inputText.

messageDetailNotInRange

String

Yes

The detail error message to be used for constructing faces messages, if input value is not with in the range, when minimum and maximum is set.

Parameters:

{0} the label that identifies the component

{1} value entered by the user

{2} the minimum allowed date

{3} the maximum allowed date

Please note: Parameter {1} which specifies the value entered by the user, should never be used in the message if the value is secure, like when secret=true on inputText.

minimum

java.util.Date

Yes

The minimum java.util.Date. ISO 8601 date strings, of the form 'yyyy-MM-dd' (for example 2004-06-22) are also allowed - the created Date object will be in the application's timezone with the time components (hours, minutes, seconds, milliseconds) zeroed-out. This will be parsed to date. When binding to Date objects, it is advised to create the Date object with zeroed-out values for any date-time components that aren't displayed (usually hours, minutes, seconds, milliseconds) to allow the largest range of values to be accepted.