You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Christoph Nenning (JIRA)" <ji...@apache.org> on 2017/05/17 09:07:04 UTC
[jira] [Created] (WW-4799) make DateConverter configurable
Christoph Nenning created WW-4799:
-------------------------------------
Summary: make DateConverter configurable
Key: WW-4799
URL: https://issues.apache.org/jira/browse/WW-4799
Project: Struts 2
Issue Type: Improvement
Components: Core
Reporter: Christoph Nenning
Priority: Minor
Currently DateConverter has some logic to test which DateFormat is able to parse given Date and use that one.
The order in which DateFormats are tested is:
* Locale specific DateTime LONG
* Locale specific DateTime MEDIUM
* Locale specific DateTime SHORT
* rfc3339 ("yyyy-MM-dd'T'HH:mm:ss")
* Locale specific Date SHORT
* Locale specific Date MEDIUM
* Locale specific Date LONG
* rfc3339dateOnly ("yyyy-MM-dd")
Would be great if apps could configure this. E.g. by:
* defining an own list
* defining order of objects in current list
* defining just one DateFormat to be used
* defining just which of Locale specific DateFormats to use (SHORT vs LONG)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)