The parameters passed to v:calendar should not be locale-dependent. I believe only the output printed to the user should depend on locales, but the syntax of parameters for web designers should be well-defined and independent from locales.
BTW it's not well-documented where to set literal locale property in order to see v:calendar example working.
Logged In: YES
user_id=1759155
Originator: YES
SEVERE: Error Rendering View[/main.xhtml]
com.sun.facelets.FaceletException: Can not set enumeration 'maxDate'
at org.rcfaces.core.internal.facelets.CameliaComponentHandler$2.applyMetadata(CameliaComponentHandler.java:95)
at com.sun.facelets.tag.MetadataImpl.applyMetadata(MetadataImpl.java:36)
[...]
Caused by: javax.faces.FacesException: You must specify a default locale for attributes !
at org.rcfaces.core.internal.tools.PageConfiguration.getAttributesLocale(PageConfiguration.java:181)
at org.rcfaces.core.internal.tools.LocaleTools.getDefaultFormat(LocaleTools.java:327)
at org.rcfaces.core.internal.tools.CalendarTools.getShortDateFormat(CalendarTools.java:334)
Logged In: YES
user_id=306652
Originator: NO
Hello,
You must specify the locale which be used to parse literal date properties :
<v:dateEntry literalLocale="fr" minDate="31/1/2000" />
<v:dateEntry literalLocale="en" value="1-31-2000" maxDate="4-3-2008"/>
But you can use the "literalLocale" property of <v:init> tag in order to define the "literalLocale" value for the whole page.
Or you can specify into the context-param "org.rcfaces.core.LITERAL_LOCALE" (web.xml) the default value for the whole application.
But I realized that I have forgotten the property "literalLocale" for the "dateItem" component !
The next release (>I2250) will add this forgotten literalLocale property.
Regards,
Olivier.