[
https://issues.jboss.org/browse/WFCORE-3304?page=com.atlassian.jira.plugi...
]
Brian Stansberry updated WFCORE-3304:
-------------------------------------
Description:
[~jamezp] said on
https://github.com/wildfly/wildfly-core/pull/2730:
we should probably use something like `DateTimeFormatter.ISO_OFFSET_DATE_TIME` so it's
a standard format that could be parsed.
Current format:
{code}
2017-09-18T22:48:24.367ZAmerica/Los_Angeles
{code}
DateTimeFormatter.ISO_OFFSET_DATE_TIME
{code}
2017-09-18T15:48:24.367-07:00
{code}
I guess another option is DateTimeFormatter.ISO_ZONED_DATE_TIME which would be
{code}
2017-09-18T15:56:21.875-07:00[America/Los_Angeles]
{code}
was:
[~jamezp] said on
https://github.com/wildfly/wildfly-core/pull/2730:
we should probably use something like `DateTimeFormatter.ISO_OFFSET_DATE_TIME` so it's
a standard format that could be parsed.
Current format:
{code}
2017-09-18T22:48:24.367ZAmerica/Los_Angeles
{code}
DateTimeFormatter.ISO_OFFSET_DATE_TIME
{code}
2017-09-18T15:48:24.367-07:00
{code}
PathInfoHandler should use a parseable format for its timestamps
----------------------------------------------------------------
Key: WFCORE-3304
URL:
https://issues.jboss.org/browse/WFCORE-3304
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Assignee: ehsavoie Hugonnet
[~jamezp] said on
https://github.com/wildfly/wildfly-core/pull/2730:
we should probably use something like `DateTimeFormatter.ISO_OFFSET_DATE_TIME` so
it's a standard format that could be parsed.
Current format:
{code}
2017-09-18T22:48:24.367ZAmerica/Los_Angeles
{code}
DateTimeFormatter.ISO_OFFSET_DATE_TIME
{code}
2017-09-18T15:48:24.367-07:00
{code}
I guess another option is DateTimeFormatter.ISO_ZONED_DATE_TIME which would be
{code}
2017-09-18T15:56:21.875-07:00[America/Los_Angeles]
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)