Irrespective of locale here, when we create a timer management rule it
takes a property called pattern where user can specify whether it's
yyyy/dd/mm, or mm/dd/yyyy etc. I don't know in advance what pattern user
wants. In this case our calendar component is not flexible enough for me
to specify don't expect for any particular pattern. The application
developer can take care of this. I'm looking for this kind of
flexibility in the component.
thx
Senthil
Bill Shannon wrote:
> Senthil Chidambaram wrote:
>
>> I'm looking for flexibility like dd/mm/yyyy, mm/dd/yyyy, or dd/mm/yy
>> (not yyyy here) etc. Right now the component takes only mm/dd/yyyy
>> format.
>
>
> Entering dd/mm/yyyy in a locale that expects mm/dd/yyyy wouldn't make
> sense.
>
> Does it change the format if you change the locale or not?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>