Date and Time Formatting"
From Documentation
m |
m |
||
| Line 6: | Line 6: | ||
= The Decision Sequence of Format = | = The Decision Sequence of Format = | ||
| − | = Application-level Format = | + | The format of date and time is decided in the following sequence. |
| − | = Per-user Format = | + | |
| + | # It checks if an attribute called <tt>org.zkoss.web.preferred.dateFormatInfo</tt> defined in the HTTP session (i.e., <javadoc type="interface">org.zkoss.zk.ui.Session</javadoc>). If so, it will be used by assuming the value is an instance or a class of <javadoc type="interface">org.zkoss.text.DateFormatInfo</javadoc>. | ||
| + | # It checks if an attribute called <tt>org.zkoss.web.preferred.dateFormatInfo</tt> defined in the servlet context (i.e., <javadoc type="interface">org.zkoss.zk.ui.Application</javadoc>). If so, it will be used by assuming the value is an instance or a class of <javadoc type="interface">org.zkoss.text.DateFormatInfo</javadoc>. | ||
| + | # It checks if a property called <tt>org.zkoss.web.preferred.dateFormatInfo</tt> defined in the library property (i.e., <javadoc >org.zkoss.lang.Library</javadoc>). If so, it will be used by assuming the value is a class of <javadoc type="interface">org.zkoss.text.DateFormatInfo</javadoc>. | ||
| + | |||
| + | With this sequence in mind, you could configure ZK to use the correct format based on the application requirements. | ||
| + | |||
| + | == Application-level Format == | ||
| + | == Per-user Format == | ||
| + | == Per-component Format == | ||
=Version History= | =Version History= | ||
{{LastUpdated}} | {{LastUpdated}} | ||
Revision as of 06:30, 25 April 2011
Overview
By default, the format of date and time, especially the format of Datebox and Timebox, is determined by the JVM's default and the current locale.
In this section, we will discuss how to configure ZK to use the format other than the JVM. For example, you could configure ZK to use the preferred format based on user's preferences.
The Decision Sequence of Format
The format of date and time is decided in the following sequence.
- It checks if an attribute called org.zkoss.web.preferred.dateFormatInfo defined in the HTTP session (i.e., Session). If so, it will be used by assuming the value is an instance or a class of DateFormatInfo.
- It checks if an attribute called org.zkoss.web.preferred.dateFormatInfo defined in the servlet context (i.e., Application). If so, it will be used by assuming the value is an instance or a class of DateFormatInfo.
- It checks if a property called org.zkoss.web.preferred.dateFormatInfo defined in the library property (i.e., Library). If so, it will be used by assuming the value is a class of DateFormatInfo.
With this sequence in mind, you could configure ZK to use the correct format based on the application requirements.
Application-level Format
Per-user Format
Per-component Format
Version History
| Version | Date | Content |
|---|---|---|
| 5.0.7 | April 2011 | The per-session format of datebox/timebox was introduced. Prior to 5.0.7, the format depends only on locale. |