[SYNCOPE-1541] XML response message timestamps missing millisecs component if "0 msecs"

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.14, 2.1.5
• Fix Version/s: 2.0.15, 2.1.6, 3.0.0-M0
• Component/s: core
• Environment: Syncope 2.1.5 instance
• Assignee: Francesco Chicchiriccò
• Reporter: J Lum
• Created: 13/Feb/20 05:13
• Updated: 29/Apr/20 07:38
• Resolved: 24/Feb/20 14:00

Description

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.