mace-opensaml-users - -2 hours after toString()
Subject: OpenSAML user discussion
List archive
- From: Sergey Kasneryk <>
- To:
- Subject: -2 hours after toString()
- Date: Fri, 6 Feb 2004 16:42:27 +0200
Hello.
Code prototype:
currentTime = "Fri Feb 06 15:47:07 EET 2004";
notOnOrAfter = "Mon Feb 16 15:47:07 EET 2004";
samlAssertion = new SAMLAssertion(issuer, currentTime,
notOnOrAfter, samlConditions, samlAdvice, samlStatements);
String xml = samlAssertion.toString();
System.out.println("xml = " + xml);
Out:
xml = <Assertion ...
<Conditions NotBefore="2004-02-06T13:47:07Z"
NotOnOrAfter="2004-02-16T13:47:07Z">
</Conditions>...
- values of NotBefore and NotOnOrAfter in a strange way lose exact 2
hours: was 15 - printed 13.
Could somebody knows a reason or a fix or a workaround?
--
Best regards,
Sergey
mailto:
- -2 hours after toString(), Sergey Kasneryk, 02/06/2004
- Re: -2 hours after toString(), Derek Atkins, 02/06/2004
- Re[2]: -2 hours after toString(), Sergey Kasneryk, 02/09/2004
- <Possible follow-up(s)>
- Re: -2 hours after toString(), matthias . seidl, 02/06/2004
- Re: -2 hours after toString(), Derek Atkins, 02/06/2004
Archive powered by MHonArc 2.6.16.