You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2020/02/13 07:08:00 UTC
[jira] [Updated] (SYNCOPE-1541) XML response message timestamps
missing millisecs component if "0 msecs"
[ https://issues.apache.org/jira/browse/SYNCOPE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò updated SYNCOPE-1541:
--------------------------------------------
Summary: XML response message timestamps missing millisecs component if "0 msecs" (was: Syncope response message timestamps missing millisecs component if "0 msecs")
> XML response message timestamps missing millisecs component if "0 msecs"
> ------------------------------------------------------------------------
>
> Key: SYNCOPE-1541
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1541
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 2.0.14, 2.1.5
> Environment: Syncope 2.1.5 instance
> Reporter: J Lum
> Priority: Minor
> Fix For: 2.0.15, 2.1.6, 3.0.0
>
>
> Reference thread on Syncope mailing list at:
> [http://syncope-user.1051894.n5.nabble.com/Possible-bug-or-Strange-or-at-least-unexpected-behavior-to-Syncope-2-1-5-REST-endpoint-tasks-executi-tc5710519.html]
> We found that the response message to the tasks/execution/recent contained a <start> timestamp that was missing the millisecs component, so we posted on the Syncope user mailing list per above. This is a request to fix that problem, i.e., to have the response timestamps to include the millisecs component even if its value is "000".
> Based on the response on the mailing list, this is due to JAXB behavior, so I suspect that the problem exist not just in the specific response mentioned above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)