| Summary: | log4j timestamps are not ISO 8601 compatible | ||
|---|---|---|---|
| Product: | Java WS Core | Reporter: | Jens-S. Vöckler <voeckler@cs.uchicago.edu> |
| Component: | globus_wsrf_core | Assignee: | Jarek Gawor <gawor@mcs.anl.gov> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | meder@mcs.anl.gov |
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
How about this format: '2002-05-23 14:04:27.166-05:00'?
AFAI understand it, and I may read it wrong, you can s/T//, but not s/T/ /. Thus, replacing "T" with space " " would not be permissable. See [2] in original request. However, one may get away on a technicality (have to re-read the draft I have here somewhere) by claiming that the Jarek's version is two timestamps, one date and one time. Note: Dropping the T is often applied to the concise (no "-" in date, no ":" in time) format. I agree that s/T/ / is more readible. We can check with XML schema what inputs xs::dateTime will accept.
Given the discussion on gt-dev (initial thread: http://www.globus.org/mail_archive/gt-dev/2006/10/msg00044.html) we decided on the following format: YYYY-MM-DDThh:mm:ss,sss[+-]hh:mm Example: 2002-05-23T14:04:27,166-05:00
Updated the log4j configuration file to print out the timestamp in the agreed format. Changes commited to trunk.