f:convertDateTime displays wrong Date [duplicate]

Answer 1

According to the JSF specs, f:convertDateTime defaults to UTC timezone (regardless of any VM timezone setting), which differs from your timezone by -1 hour (standard time) or -2 hours (summer time).

We use a application scoped page bean with an timeZone property like this:

public TimeZone getTimeZone() {
    return TimeZone.getDefault();
}

Then we use the property in an EL expression:

<ice:outputText value="#{deliveryDate}">
    <f:convertDateTime type="both" timeZone="#{Application.timeZone}" />
</ice:outputText>

The advantage is that it's considering standard/summer time automatically.

Answer 2

You are probably having issues with the Time zones.

Check this article on how to resolve them.

Before that, you can try explicitly setting the timeZone attribute of <f:convertDataTime>

Answer 3

<h:outputText id="dateId" value="#{item.date}">
 <f:convertDateTime for="dateId" type="date" dateStyle="long" locale="pl"/>   </h:outputText>

Answer 4

JSF defaults to UTC timezone for date/time converters. To override this you need to set the timeZone attribute in every date/time converter. Here's an example using EDT timezone (assuming you're on the east of US).

<f:convertDateTime locale="en_US" type="both" dateStyle="short" timeZone="EDT" />

The locale attribute only controls the full day/month name formatting (it becomes English).

If you want to override the default UTC timezone to be the operating platform default timezone, then you need to add the following context param to web.xml:

<context-param>
    <param-name>javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE</param-name>
    <param-value>true</param-value>
</context-param>

Then you don't need to edit every individual JSF <f:convertXxx> tag.

Answer 5

We had the same problem and ended up with writing a new JSF converter that uses a SimpleDateFormat created with new SimpleDateFormat(String pattern) for the date conversion.