> Hi Matthias,
>
> I believe this is the dreaded converter timezone problem which can be
> fixed by using your own special converter.
>
> What I generally do is put a component-binding on the calendar
> component and then create the component in the backend, and there I
> set stuff which is repeatable across the whole app (like a
> converter="#{converterBean.converter}") and styles.

Thanks. This sounds a little bit complicated for the apparently small
problem.

How does this converter have to look like? Can't I use the convertDateTime
standard action?

-Matthias

> regards,
>
> Martin
>
> On 3/20/06, Matthias Kahlau <[EMAIL PROTECTED]> wrote:
> > Hi!
> >
> >
> > I have a date "18.3.2006" shown in an outputText with a nested
> > convertDateTime with timeZone="Europe/Berlin". If I open an
> edit form with
> > this date "18.3.2006", the date is shown in an inputCalendar,
> also with a
> > nested convertDateTime with timeZone="Europe/Berlin".
> >
> > The problem is that the date is then shown as "19.3.2006". Does the
> > inputCalendar convert the date itself to another TimeZone?
> >
> > Thanks.
> >
> >
> > -Matthias
> >
> >
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces

Reply via email to