[
https://issues.apache.org/jira/browse/WW-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262172#comment-17262172
]
ASF subversion and git services commented on WW-4799:
-----------------------------------------------------
Commit d876a2ad930e41dca3a05f8ba252cb16e92aa3d7 in struts's branch
refs/heads/WW-4799-conversion-format from Cabasson, Denis - CoSD/DSCo
[ https://gitbox.apache.org/repos/asf?p=struts.git;h=d876a2a ]
WW-4799 Adding struts.date.format as a conversion format for DateConverter
> 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
> Fix For: 2.6
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
