Use of Date with ADF

Date creates many confusion & bugs in our applications, some of which are only found when Day Light Savings time changes. :)

There is fundamental issue with how we talk about Date. For example, my date is in Central Time or for this Location my Date is in Eastern Time. As we all know, Date is milliseconds representing GMT time & String value we see in Debugger or Logs is just String representation of Date with respect to some TimeZone.

Here is what i recommend for Date usage with ADF, some of which can very well apply to other frameworks as well.

1. Don't offset date value for Persistence

JDBC driver will transform value of Date is Server's Default TimeZone for storing in Table Column. At times, we try to offset value of Date, so that when JDBC Driver creates String representation using Server's Default TimeZone, it looks like GMT for example. This is clever, but not a good idea.

This approach can cause issues with Queries. It will also not represent values correctly on screen components. You can workaround these issues, but that's extra work that can be avoided, by accepting the fact that Date will be stored in Server's Default TimeZone.

2. Do not specify Date Format on Control Hints for Entity or View Object attributes

ADF does a good job of providing Control Hints that can be set on Business Components, but in this case I would recommend not setting any Format for Date on Entity and View Object. I have seen issues with Control Hints related to Date Format and more importantly it makes sense to control this based on User's Preferences / Locale.

3. Create Session Scope variables for TimeZone & Date Format

Using Phase Listener, create Session Scope values for TimeZone and various Date & Time formats. You can read this values from User's Preference or derive it using any other data store.

These can be used in UI pages with af:convertDateTime as shown below.

 

4. Specify TimeZone in trinidad-config.xml

If you set value of time-zone in trinidad-config.xml, it will apply to all Date components for display and input processing.

5. Specify Pattern on af:date Specify different TimeZone if necessary on af:date

If you want to display particular Date value in a different TimeZone, you can indicate that on af:convertDateTime. For example, Delivery Date would make sense to be displayed in TimeZone of Delivery Location.

af:poll not working

ADF Faces provides poll component, it's description & sample use cases are documented on Tag Documentation as shown below.

The poll component delivers PollEvents to the server at fixed intervals. This can be used either for steady updates, or to deliver a heartbeat to keep a user logged in, or to warn a user about to be logged out (for some examples).

One classic use of Poll component would be to keep User Session active as long as browser window is open. In this case, you will set Poll Interval (interval) and dummy pollListener. Poll Listener can be empty method, it does not have to do anything. Poll Interval should be less than HTTP Session Timeout. HTTP Session Timeout is setup in web.xml.

Such use of Poll component fails to keep User Session active, after upgrading from 11.1.1.3. This is due to new attribute timeout for af:poll, value for which defaults to 10 minutes (This property is added with 11.1.1.4). So if user does not perform any activity on Keyboard or Mouse for 10 minutes, Poll component will stop delivering any Poll Events. If you are using af:poll to keep User Session (by sending regular heartbeat) active, add timeout property to af:poll with very high value to avoid stopping Poll Events.