-
1. Re: Calendar client side?
amitev Sep 14, 2007 12:59 AM (in response to bruno.arruda)I also think that the calendar should not be ajax only.
-
2. Re: Calendar client side?
ilya_shaikovsky Sep 14, 2007 1:24 PM (in response to bruno.arruda)You may use preloadDateBegin and preloadDateEnd attributes. The whole period will be loaded to client
-
3. Re: Calendar client side?
bruno.arruda Sep 14, 2007 4:03 PM (in response to bruno.arruda)Thanks Ilya,
I tried to find an example on how to use it on SVN but didn´t find any...
I tried with no success:<rich:calendar preloadDateRangeBegin="01/01/2007" preloadDateRangeEnd="01/01/2008" value="#{crudProcess.expirationDate}" datePattern="dd/MM/yyyy" />
can you please give us a light on that ?
Thanks very much again.
Best Regards, -
4. Re: Calendar client side?
bruno.arruda Sep 17, 2007 12:46 PM (in response to bruno.arruda)anyone got it working?
-
5. Re: Calendar client side?
j-pro Sep 17, 2007 1:20 PM (in response to bruno.arruda)"bruno.arruda" wrote:
anyone got it working?
Having:<rich:calendar id="employeeDocumentDateEdit" value="#{amBean.employee.documentDate}" enableManualInput="true" popup="true" locale="#{amBean.calendarLocale}" datePattern="dd.MM.yyyy" preloadDateRangeBegin="01.01.2001" preloadDateRangeEnd="01.01.2002" showInput="true" required="true"/>
I get:org.jboss.util.NestedRuntimeException: Unparseable date: "01.01.2000"; - nested throwable: (java.text.ParseException: Unparseable date: "01.01.2000")
-
6. Re: Calendar client side?
j-pro Sep 17, 2007 1:22 PM (in response to bruno.arruda)There is written "Unparseable date: "01.01.2000"", because first it was 2000. Then I've changed to 2001 - the same exception.
-
7. Re: Calendar client side?
maksimkaszynski Sep 17, 2007 1:50 PM (in response to bruno.arruda)I see, we need to use converters for all date-typed properties.
http://jira.jboss.com/jira/browse/RF-950 -
8. Re: Calendar client side?
maksimkaszynski Sep 17, 2007 2:09 PM (in response to bruno.arruda)"J-Pro" wrote:
There is written "Unparseable date: "01.01.2000"", because first it was 2000. Then I've changed to 2001 - the same exception.
Problem is that preloadDateRange attributes currently accept only Date value. No converter is applied. Facelets use ExpressionFactory to convert string attribute value to Date. JSP does nothing at all. -
9. Re: Calendar client side?
bruno.arruda Sep 17, 2007 2:28 PM (in response to bruno.arruda)Thanks Jpro and maksim,
I will ke an eye on that one.
Regards, -
10. Re: Calendar client side?
j-pro Sep 17, 2007 2:31 PM (in response to bruno.arruda)Thanks, maksimkaszynski.
-
11. Re: Calendar client side?
bruno.arruda Sep 17, 2007 2:47 PM (in response to bruno.arruda)I also tried with managedbean with a Date attribute but it didnt work...
On JSP:<rich:calendar preloadDateRangeBegin="#{mainCustomer.preloadDateRangeBegin}" preloadDateRangeEnd="#{mainCustomer.preloadDateRangeEnd}" value="#{crudProcess.expirationDate}" datePattern="dd/MM/yyyy" />
On ManagedBean:GregorianCalendar grego = new GregorianCalendar(); grego.set( GregorianCalendar.DAY_OF_MONTH,1); grego.set( GregorianCalendar.MONTH,0); grego.set( GregorianCalendar.YEAR,2006); preloadDateRangeBegin = new Date(grego.getTimeInMillis()); grego.set( GregorianCalendar.DAY_OF_MONTH,1); grego.set( GregorianCalendar.MONTH,0); grego.set( GregorianCalendar.YEAR,2009); preloadDateRangeEnd = new Date(grego.getTimeInMillis());
-
12. Re: Calendar client side?
bruno.arruda Sep 17, 2007 2:48 PM (in response to bruno.arruda)Just to clarify, no error but no pre-rendering
-
13. Re: Calendar client side?
ilya_shaikovsky Sep 18, 2007 6:51 AM (in response to bruno.arruda)sorry. just our fault. preload should works only for client side mode.
We have no such mode now. http://jira.jboss.com/jira/browse/RF-955 added. Will be added ASAP. -
14. Re: Calendar client side?
bruno.arruda Sep 18, 2007 9:58 AM (in response to bruno.arruda)thanks Ilya.