mace-opensaml-users - RE: Milliseconds in IssueInstant and other tinmevalues
Subject: OpenSAML user discussion
List archive
- From: Scott Cantor <>
- To: 'Svein Otto Solem' <>,
- Subject: RE: Milliseconds in IssueInstant and other tinmevalues
- Date: Fri, 09 Jan 2004 10:45:04 -0500
- Importance: Normal
- Organization: The Ohio State University
Title: Message
As far
as I know, I fixed that bug a while back in Java, and I don't think the C++
ever had it, because the Xerces DateTime class should handle the parsing. The
fix for Java should be in cvs.
--
Scott
-----Original Message-----
From: Svein Otto Solem [mailto:]
Sent: Friday, January 09, 2004 10:42 AM
To:
Subject: Milliseconds in IssueInstant and other tinmevaluesA "SAMLServer" not using openSAML sends requests containing AssertionsArtifact. In this message all datetime has format using milliseconds. I get a parsing error ! Any solution ? (for now I just added ".SSS" to the input parameter to SimpleDateFormat constructor everywhere i saw it in use, but this is only a temporarily solution!)Svein Otto SolemKantega.no
- Milliseconds in IssueInstant and other tinmevalues, Svein Otto Solem, 01/09/2004
- RE: Milliseconds in IssueInstant and other tinmevalues, Scott Cantor, 01/09/2004
Archive powered by MHonArc 2.6.16.