[
https://issues.apache.org/jira/browse/WW-4799?focusedWorklogId=540556&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-540556
]
ASF GitHub Bot logged work on WW-4799:
--------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/21 16:18
Start Date: 23/Jan/21 16:18
Worklog Time Spent: 10m
Work Description: lukaszlenart commented on pull request #468:
URL: https://github.com/apache/struts/pull/468#issuecomment-766112377
LGTM 👍
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 540556)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
