Uploaded image for project: 'Syncope'
  1. Syncope
  2. SYNCOPE-1541

XML response message timestamps missing millisecs component if "0 msecs"

    XMLWordPrintableJSON

    Details

    • 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
    • Component/s: core
    • Labels:
      None
    • Environment:
      Syncope 2.1.5 instance

      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.

        Attachments

          Activity

            People

            • Assignee:
              ilgrosso Francesco Chicchiriccò
              Reporter:
              ohaya@yahoo.com J Lum
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: