Anonymous_User Absent Member.
Absent Member.
1673 views

SetTimeStamp Request

Hi,

I'm working much with the SetTimeStamp request. (Archiving App. !!)

Now I would like to have a way to completely reset the timestamp (as if
I never had set it - like a new Mailbox). When I do a GetTimestamp on a
new Mailbox I get back 000000000T00000000Z (or similar).
I have found out that the earliest time I can set is 19700101T000001Z
any timestamp before is ignored and not set although the Status of the
request came back as OK.
So, What value do I have to send to completely reset the timestamp
(restore the 'virgin' state) ?

Thanks in advance

Labels (1)
0 Likes
7 Replies
Anonymous_User Absent Member.
Absent Member.

Re: SetTimeStamp Request

I'll entry a bug to look at the problem.
Thanks.
Preston

>>> On Friday, February 08, 2008 at 4:08 AM, Rainer

Backes<rbackesno@spambond.de>
wrote:
> Hi,
>
> I'm working much with the SetTimeStamp request. (Archiving App. !!)
>
> Now I would like to have a way to completely reset the timestamp (as if
> I never had set it - like a new Mailbox). When I do a GetTimestamp on a
> new Mailbox I get back 000000000T00000000Z (or similar).
> I have found out that the earliest time I can set is 19700101T000001Z
> any timestamp before is ignored and not set although the Status of the
> request came back as OK.
> So, What value do I have to send to completely reset the timestamp
> (restore the 'virgin' state) ?
>
> Thanks in advance

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SetTimeStamp Request

I put the fix to Bonsai.

With the fix, the trick is to get the value to 0.
I've attached what java and .NET do.
reset.cs is the code in C#.
reset.java is the code in Java.
reset.xml is the SOAP trace of the Java code.
reset_ms.xml is the SOAP trace of the C# code.

reset.cs:
private void miTestItem_Click(object sender, EventArgs e)
{
System.DateTime date = new DateTime(0);

WebReference.setTimestampRequest req = new
vcsClient.WebReference.setTimestampRequest();
req.backup = date;
req.backupSpecified = true;
req.retention = date;
req.retentionSpecified = true;
ws.setTimestampRequest(req);
}

reset.java:
public void testReset() {
Calendar cDate = Calendar.getInstance();
cDate.setTimeInMillis( 0 );

try {
m_main.getService().setTimestampRequest( cDate, cDate,
m_main.getSessionId(), m_main.getTrace()
);
}
catch ( Exception e ) {
e.printStackTrace();
}
}

reset.xml:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns0="http://schemas.novell.com/2005/01/GroupWise/methods">
<env:Header>
<ans1:session
xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">rCxXdJSKpexgv
BgL</ans1:session>
<ans1:gwTrace
xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">false</ans1:g
wTrace>
</env:Header>
<env:Body>
<ns0:setTimestampRequest>
<ns0:backup>1969-12-31T17:00:00.000-07:00</ns0:backup>
<ns0:retention>1969-12-31T17:00:00.000-07:00</ns0:retention>
</ns0:setTimestampRequest>
</env:Body>
</env:Envelope>

reset_ms.xml:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header>
<session
xmlns="http://schemas.novell.com/2005/01/GroupWise/types">e5Ypcx1c9xWOPtvg</
session>
</soap:Header>
<soap:Body>
<setTimestampRequest
xmlns="http://schemas.novell.com/2005/01/GroupWise/methods">
<backup>0001-01-01T00:00:00</backup>
<retention>0001-01-01T00:00:00</retention>
</setTimestampRequest>
</soap:Body>
</soap:Envelope>

Sorry, I had to put the attachments inline.
Let me know if you have questions.

Preston

>>> On Friday, February 08, 2008 at 5:16 AM, Preston

Stephenson<PStephenson@gw.novell.com> wrote:
> I'll entry a bug to look at the problem.
> Thanks.
> Preston
>
>>>> On Friday, February 08, 2008 at 4:08 AM, Rainer

> Backes<rbackesno@spambond.de>
> wrote:
>> Hi,
>>
>> I'm working much with the SetTimeStamp request. (Archiving App. !!)
>>
>> Now I would like to have a way to completely reset the timestamp (as if
>> I never had set it - like a new Mailbox). When I do a GetTimestamp on a
>> new Mailbox I get back 000000000T00000000Z (or similar).
>> I have found out that the earliest time I can set is 19700101T000001Z
>> any timestamp before is ignored and not set although the Status of the
>> request came back as OK.
>> So, What value do I have to send to completely reset the timestamp
>> (restore the 'virgin' state) ?
>>
>> Thanks in advance

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SetTimeStamp Request

So you simply changed the code to set any time before
1970-01-01T00:00:00Z to 0 instead of ignoring the request ?
So GroupWise works internaly with Unix-like times ?

Thanks

Rainer


Preston Stephenson schrieb:
> I put the fix to Bonsai.
>
> With the fix, the trick is to get the value to 0.
> I've attached what java and .NET do.
> reset.cs is the code in C#.
> reset.java is the code in Java.
> reset.xml is the SOAP trace of the Java code.
> reset_ms.xml is the SOAP trace of the C# code.
>
> reset.cs:
> private void miTestItem_Click(object sender, EventArgs e)
> {
> System.DateTime date = new DateTime(0);
>
> WebReference.setTimestampRequest req = new
> vcsClient.WebReference.setTimestampRequest();
> req.backup = date;
> req.backupSpecified = true;
> req.retention = date;
> req.retentionSpecified = true;
> ws.setTimestampRequest(req);
> }
>
> reset.java:
> public void testReset() {
> Calendar cDate = Calendar.getInstance();
> cDate.setTimeInMillis( 0 );
>
> try {
> m_main.getService().setTimestampRequest( cDate, cDate,
> m_main.getSessionId(), m_main.getTrace()
> );
> }
> catch ( Exception e ) {
> e.printStackTrace();
> }
> }
>
> reset.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <env:Envelope
> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:ns0="http://schemas.novell.com/2005/01/GroupWise/methods">
> <env:Header>
> <ans1:session
> xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">rCxXdJSKpexgv
> BgL</ans1:session>
> <ans1:gwTrace
> xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">false</ans1:g
> wTrace>
> </env:Header>
> <env:Body>
> <ns0:setTimestampRequest>
> <ns0:backup>1969-12-31T17:00:00.000-07:00</ns0:backup>
> <ns0:retention>1969-12-31T17:00:00.000-07:00</ns0:retention>
> </ns0:setTimestampRequest>
> </env:Body>
> </env:Envelope>
>
> reset_ms.xml:
> <?xml version="1.0" encoding="utf-8"?>
> <soap:Envelope
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <soap:Header>
> <session
> xmlns="http://schemas.novell.com/2005/01/GroupWise/types">e5Ypcx1c9xWOPtvg</
> session>
> </soap:Header>
> <soap:Body>
> <setTimestampRequest
> xmlns="http://schemas.novell.com/2005/01/GroupWise/methods">
> <backup>0001-01-01T00:00:00</backup>
> <retention>0001-01-01T00:00:00</retention>
> </setTimestampRequest>
> </soap:Body>
> </soap:Envelope>
>
> Sorry, I had to put the attachments inline.
> Let me know if you have questions.
>
> Preston
>
>>>> On Friday, February 08, 2008 at 5:16 AM, Preston

> Stephenson<PStephenson@gw.novell.com> wrote:
>> I'll entry a bug to look at the problem.
>> Thanks.
>> Preston
>>
>>>>> On Friday, February 08, 2008 at 4:08 AM, Rainer

>> Backes<rbackesno@spambond.de>
>> wrote:
>>> Hi,
>>>
>>> I'm working much with the SetTimeStamp request. (Archiving App. !!)
>>>
>>> Now I would like to have a way to completely reset the timestamp (as if
>>> I never had set it - like a new Mailbox). When I do a GetTimestamp on a
>>> new Mailbox I get back 000000000T00000000Z (or similar).
>>> I have found out that the earliest time I can set is 19700101T000001Z
>>> any timestamp before is ignored and not set although the Status of the
>>> request came back as OK.
>>> So, What value do I have to send to completely reset the timestamp
>>> (restore the 'virgin' state) ?
>>>
>>> Thanks in advance

>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SetTimeStamp Request

Internally we store times as the number of seconds since Jan 1, 1970.
If the string time can be converted to 0 seconds, then I have a test
for the seconds being 0.

Preston

>>> On Thursday, March 27, 2008 at 6:08 AM, Rainer

Backes<rbackesno@spambond.de>
wrote:
> So you simply changed the code to set any time before
> 1970-01-01T00:00:00Z to 0 instead of ignoring the request ?
> So GroupWise works internaly with Unix-like times ?
>
> Thanks
>
> Rainer
>
>
> Preston Stephenson schrieb:
>> I put the fix to Bonsai.
>>
>> With the fix, the trick is to get the value to 0.
>> I've attached what java and .NET do.
>> reset.cs is the code in C#.
>> reset.java is the code in Java.
>> reset.xml is the SOAP trace of the Java code.
>> reset_ms.xml is the SOAP trace of the C# code.
>>
>> reset.cs:
>> private void miTestItem_Click(object sender, EventArgs e)
>> {
>> System.DateTime date = new DateTime(0);
>>
>> WebReference.setTimestampRequest req = new
>> vcsClient.WebReference.setTimestampRequest();
>> req.backup = date;
>> req.backupSpecified = true;
>> req.retention = date;
>> req.retentionSpecified = true;
>> ws.setTimestampRequest(req);
>> }
>>
>> reset.java:
>> public void testReset() {
>> Calendar cDate = Calendar.getInstance();
>> cDate.setTimeInMillis( 0 );
>>
>> try {
>> m_main.getService().setTimestampRequest( cDate, cDate,
>> m_main.getSessionId(),

m_main.getTrace()
>> );
>> }
>> catch ( Exception e ) {
>> e.printStackTrace();
>> }
>> }
>>
>> reset.xml:
>> <?xml version="1.0" encoding="UTF-8"?>
>> <env:Envelope
>> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
>> xmlns:ns0="http://schemas.novell.com/2005/01/GroupWise/methods">
>> <env:Header>
>> <ans1:session
>>

xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">rCxXdJSKpexgv

>> BgL</ans1:session>
>> <ans1:gwTrace
>>

xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">false</ans1:g

>> wTrace>
>> </env:Header>
>> <env:Body>
>> <ns0:setTimestampRequest>
>> <ns0:backup>1969-12-31T17:00:00.000-07:00</ns0:backup>
>> <ns0:retention>1969-12-31T17:00:00.000-07:00</ns0:retention>
>> </ns0:setTimestampRequest>
>> </env:Body>
>> </env:Envelope>
>>
>> reset_ms.xml:
>> <?xml version="1.0" encoding="utf-8"?>
>> <soap:Envelope
>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> <soap:Header>
>> <session
>>

xmlns="http://schemas.novell.com/2005/01/GroupWise/types">e5Ypcx1c9xWOPtvg</

>> session>
>> </soap:Header>
>> <soap:Body>
>> <setTimestampRequest
>> xmlns="http://schemas.novell.com/2005/01/GroupWise/methods">
>> <backup>0001-01-01T00:00:00</backup>
>> <retention>0001-01-01T00:00:00</retention>
>> </setTimestampRequest>
>> </soap:Body>
>> </soap:Envelope>
>>
>> Sorry, I had to put the attachments inline.
>> Let me know if you have questions.
>>
>> Preston
>>
>>>>> On Friday, February 08, 2008 at 5:16 AM, Preston

>> Stephenson<PStephenson@gw.novell.com> wrote:
>>> I'll entry a bug to look at the problem.
>>> Thanks.
>>> Preston
>>>
>>>>>> On Friday, February 08, 2008 at 4:08 AM, Rainer
>>> Backes<rbackesno@spambond.de>
>>> wrote:
>>>> Hi,
>>>>
>>>> I'm working much with the SetTimeStamp request. (Archiving App. !!)
>>>>
>>>> Now I would like to have a way to completely reset the timestamp (as if


>>>> I never had set it - like a new Mailbox). When I do a GetTimestamp on a


>>>> new Mailbox I get back 000000000T00000000Z (or similar).
>>>> I have found out that the earliest time I can set is 19700101T000001Z
>>>> any timestamp before is ignored and not set although the Status of the


>>>> request came back as OK.
>>>> So, What value do I have to send to completely reset the timestamp
>>>> (restore the 'virgin' state) ?
>>>>
>>>> Thanks in advance

>>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SetTimeStamp Request

It hit me again:

When the timestamp had never been touched, it comes back as 0, which is
for Groupwise 1970-01-01T00:00:00Z. The SOAP Interface delivers
something like 0000-01-01T00:00:00Z.
This can lead to unpredictable results for diffrent programming
languages, that use diffrent ways to encode time.
My suggestion is here, that when a Mailbox has never been touched, the
SOAP interface should reply with 1970-01-01T00:00:00Z for GetTimeStamp.
And the documentation should state this as the earliest possible value.

Thanks

Rainer


Preston Stephenson schrieb:
> Internally we store times as the number of seconds since Jan 1, 1970.
> If the string time can be converted to 0 seconds, then I have a test
> for the seconds being 0.
>
> Preston
>
>>>> On Thursday, March 27, 2008 at 6:08 AM, Rainer

> Backes<rbackesno@spambond.de>
> wrote:
>> So you simply changed the code to set any time before
>> 1970-01-01T00:00:00Z to 0 instead of ignoring the request ?
>> So GroupWise works internaly with Unix-like times ?
>>
>> Thanks
>>
>> Rainer
>>
>>
>> Preston Stephenson schrieb:
>>> I put the fix to Bonsai.
>>>
>>> With the fix, the trick is to get the value to 0.
>>> I've attached what java and .NET do.
>>> reset.cs is the code in C#.
>>> reset.java is the code in Java.
>>> reset.xml is the SOAP trace of the Java code.
>>> reset_ms.xml is the SOAP trace of the C# code.
>>>
>>> reset.cs:
>>> private void miTestItem_Click(object sender, EventArgs e)
>>> {
>>> System.DateTime date = new DateTime(0);
>>>
>>> WebReference.setTimestampRequest req = new
>>> vcsClient.WebReference.setTimestampRequest();
>>> req.backup = date;
>>> req.backupSpecified = true;
>>> req.retention = date;
>>> req.retentionSpecified = true;
>>> ws.setTimestampRequest(req);
>>> }
>>>
>>> reset.java:
>>> public void testReset() {
>>> Calendar cDate = Calendar.getInstance();
>>> cDate.setTimeInMillis( 0 );
>>>
>>> try {
>>> m_main.getService().setTimestampRequest( cDate, cDate,
>>> m_main.getSessionId(),

> m_main.getTrace()
>>> );
>>> }
>>> catch ( Exception e ) {
>>> e.printStackTrace();
>>> }
>>> }
>>>
>>> reset.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <env:Envelope
>>> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
>>> xmlns:ns0="http://schemas.novell.com/2005/01/GroupWise/methods">
>>> <env:Header>
>>> <ans1:session
>>>

> xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">rCxXdJSKpexgv
>
>>> BgL</ans1:session>
>>> <ans1:gwTrace
>>>

> xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">false</ans1:g
>
>>> wTrace>
>>> </env:Header>
>>> <env:Body>
>>> <ns0:setTimestampRequest>
>>> <ns0:backup>1969-12-31T17:00:00.000-07:00</ns0:backup>
>>> <ns0:retention>1969-12-31T17:00:00.000-07:00</ns0:retention>
>>> </ns0:setTimestampRequest>
>>> </env:Body>
>>> </env:Envelope>
>>>
>>> reset_ms.xml:
>>> <?xml version="1.0" encoding="utf-8"?>
>>> <soap:Envelope
>>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>>> <soap:Header>
>>> <session
>>>

> xmlns="http://schemas.novell.com/2005/01/GroupWise/types">e5Ypcx1c9xWOPtvg</
>
>>> session>
>>> </soap:Header>
>>> <soap:Body>
>>> <setTimestampRequest
>>> xmlns="http://schemas.novell.com/2005/01/GroupWise/methods">
>>> <backup>0001-01-01T00:00:00</backup>
>>> <retention>0001-01-01T00:00:00</retention>
>>> </setTimestampRequest>
>>> </soap:Body>
>>> </soap:Envelope>
>>>
>>> Sorry, I had to put the attachments inline.
>>> Let me know if you have questions.
>>>
>>> Preston
>>>
>>>>>> On Friday, February 08, 2008 at 5:16 AM, Preston
>>> Stephenson<PStephenson@gw.novell.com> wrote:
>>>> I'll entry a bug to look at the problem.
>>>> Thanks.
>>>> Preston
>>>>
>>>>>>> On Friday, February 08, 2008 at 4:08 AM, Rainer
>>>> Backes<rbackesno@spambond.de>
>>>> wrote:
>>>>> Hi,
>>>>>
>>>>> I'm working much with the SetTimeStamp request. (Archiving App. !!)
>>>>>
>>>>> Now I would like to have a way to completely reset the timestamp (as if

>
>>>>> I never had set it - like a new Mailbox). When I do a GetTimestamp on a

>
>>>>> new Mailbox I get back 000000000T00000000Z (or similar).
>>>>> I have found out that the earliest time I can set is 19700101T000001Z
>>>>> any timestamp before is ignored and not set although the Status of the

>
>>>>> request came back as OK.
>>>>> So, What value do I have to send to completely reset the timestamp
>>>>> (restore the 'virgin' state) ?
>>>>>
>>>>> Thanks in advance

>


0 Likes
vip8439 Absent Member.
Absent Member.

Re: SetTimeStamp Request

So Groupwise expects the time in epoch? The format of the date/time being passed appears as though it should be UTC so I believe I may be misunderstanding something here which may be causing my issue. I am using setTimestampRequest to set the retention date and sending the date in UTC in the exact format in the Novell SOAP docs example. 20090415T084345Z. However, when I perform the getTimestampRequest, Groupwise returns 2009-04-15 08:43:45+06:00. According to the documentation, the date/time in the getTimestampResponse should be in the same format as what was sent in the setTimestampRequest. The time in the getTimestampResponse is correct as far as local time goes; however, the +06:00 worries me as I would not expect a time zone to be given back and my timezone on the server is CST(-6) or -5 with daylight savings, not +6. I would expect the server to give me the time back in UTC since the retention/archiving application could theoretically be running from a time zone that is different from the time zone where the Groupwise server is or be moved to other time zones after deployment. Also I would expect the server to return UTC time since I set the timestamp in UTC. Am I missing a setting somewhere or going about this completely wrong? Groupwise 8.0

Rainer Backes;1756183 wrote:
It hit me again:

When the timestamp had never been touched, it comes back as 0, which is
for Groupwise 1970-01-01T00:00:00Z. The SOAP Interface delivers
something like 0000-01-01T00:00:00Z.
This can lead to unpredictable results for diffrent programming
languages, that use diffrent ways to encode time.
My suggestion is here, that when a Mailbox has never been touched, the
SOAP interface should reply with 1970-01-01T00:00:00Z for GetTimeStamp.
And the documentation should state this as the earliest possible value.

Thanks

Rainer


Preston Stephenson schrieb:
> Internally we store times as the number of seconds since Jan 1, 1970.
> If the string time can be converted to 0 seconds, then I have a test
> for the seconds being 0.
>
> Preston
>
>>>> On Thursday, March 27, 2008 at 6:08 AM, Rainer

> Backes<rbackesno@spambond.de>
> wrote:
>> So you simply changed the code to set any time before
>> 1970-01-01T00:00:00Z to 0 instead of ignoring the request ?
>> So GroupWise works internaly with Unix-like times ?
>>
>> Thanks
>>
>> Rainer
>>
>>
>> Preston Stephenson schrieb:
>>> I put the fix to Bonsai.
>>>
>>> With the fix, the trick is to get the value to 0.
>>> I've attached what java and .NET do.
>>> reset.cs is the code in C#.
>>> reset.java is the code in Java.
>>> reset.xml is the SOAP trace of the Java code.
>>> reset_ms.xml is the SOAP trace of the C# code.
>>>
>>> reset.cs:
>>> private void miTestItem_Click(object sender, EventArgs e)
>>> {
>>> System.DateTime date = new DateTime(0);
>>>
>>> WebReference.setTimestampRequest req = new
>>> vcsClient.WebReference.setTimestampRequest();
>>> req.backup = date;
>>> req.backupSpecified = true;
>>> req.retention = date;
>>> req.retentionSpecified = true;
>>> ws.setTimestampRequest(req);
>>> }
>>>
>>> reset.java:
>>> public void testReset() {
>>> Calendar cDate = Calendar.getInstance();
>>> cDate.setTimeInMillis( 0 );
>>>
>>> try {
>>> m_main.getService().setTimestampRequest( cDate, cDate,
>>> m_main.getSessionId(),

> m_main.getTrace()
>>> );
>>> }
>>> catch ( Exception e ) {
>>> e.printStackTrace();
>>> }
>>> }
>>>
>>> reset.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <env:Envelope
>>> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
>>> xmlns:ns0="http://schemas.novell.com/2005/01/GroupWise/methods">
>>> <env:Header>
>>> <ans1:session
>>>

> xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">rCxXdJSKpexgv
>
>>> BgL</ans1:session>
>>> <ans1:gwTrace
>>>

> xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">false</ans1:g
>
>>> wTrace>
>>> </env:Header>
>>> <env:Body>
>>> <ns0:setTimestampRequest>
>>> <ns0:backup>1969-12-31T17:00:00.000-07:00</ns0:backup>
>>> <ns0:retention>1969-12-31T17:00:00.000-07:00</ns0:retention>
>>> </ns0:setTimestampRequest>
>>> </env:Body>
>>> </env:Envelope>
>>>
>>> reset_ms.xml:
>>> <?xml version="1.0" encoding="utf-8"?>
>>> <soap:Envelope
>>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>>> <soap:Header>
>>> <session
>>>

> xmlns="http://schemas.novell.com/2005/01/GroupWise/types">e5Ypcx1c9xWOPtvg</
>
>>> session>
>>> </soap:Header>
>>> <soap:Body>
>>> <setTimestampRequest
>>> xmlns="http://schemas.novell.com/2005/01/GroupWise/methods">
>>> <backup>0001-01-01T00:00:00</backup>
>>> <retention>0001-01-01T00:00:00</retention>
>>> </setTimestampRequest>
>>> </soap:Body>
>>> </soap:Envelope>
>>>
>>> Sorry, I had to put the attachments inline.
>>> Let me know if you have questions.
>>>
>>> Preston
>>>
>>>>>> On Friday, February 08, 2008 at 5:16 AM, Preston
>>> Stephenson<PStephenson@gw.novell.com> wrote:
>>>> I'll entry a bug to look at the problem.
>>>> Thanks.
>>>> Preston
>>>>
>>>>>>> On Friday, February 08, 2008 at 4:08 AM, Rainer
>>>> Backes<rbackesno@spambond.de>
>>>> wrote:
>>>>> Hi,
>>>>>
>>>>> I'm working much with the SetTimeStamp request. (Archiving App. !!)
>>>>>
>>>>> Now I would like to have a way to completely reset the timestamp (as if

>
>>>>> I never had set it - like a new Mailbox). When I do a GetTimestamp on a

>
>>>>> new Mailbox I get back 000000000T00000000Z (or similar).
>>>>> I have found out that the earliest time I can set is 19700101T000001Z
>>>>> any timestamp before is ignored and not set although the Status of the

>
>>>>> request came back as OK.
>>>>> So, What value do I have to send to completely reset the timestamp
>>>>> (restore the 'virgin' state) ?
>>>>>
>>>>> Thanks in advance

>
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SetTimeStamp Request

Are you saying the +06:00 is in your application
or in the SOAP trace?
At least Java applies a timezone / offset to the
values when they are sent in the SOAP trace.
I haven't figured out how to force it not to.

Preston

>>> On Wednesday, April 15, 2009 at 12:26 PM,

vip8439<vip8439@no-mx.forums.novell.com> wrote:

> So Groupwise expects the time in epoch? The format of the date/time
> being passed appears as though it should be UTC so I believe I may be
> misunderstanding something here which may be causing my issue. I am
> using setTimestampRequest to set the retention date and sending the date
> in UTC in the exact format in the Novell SOAP docs example.
> 20090415T084345Z. However, when I perform the getTimestampRequest,
> Groupwise returns 2009-04-15 08:43:45+06:00. According to the
> documentation, the date/time in the getTimestampResponse should be in
> the same format as what was sent in the setTimestampRequest. The time
> in the getTimestampResponse is correct as far as local time goes;
> however, the +06:00 worries me as I would not expect a time zone to be
> given back and my timezone on the server is CST(-6) or -5 with daylight
> savings, not +6. I would expect the server to give me the time back in
> UTC since the retention/archiving application could theoretically be
> running from a time zone that is different from the time zone where the
> Groupwise server is or be moved to other time zones after deployment.
> Also I would expect the server to return UTC time since I set the
> timestamp in UTC. Am I missing a setting somewhere or going about this
> completely wrong? Groupwise 8.0
>
> Rainer Backes;1756183 Wrote:
>> It hit me again:
>>
>> When the timestamp had never been touched, it comes back as 0, which
>> is
>> for Groupwise 1970-01-01T00:00:00Z. The SOAP Interface delivers
>> something like 0000-01-01T00:00:00Z.
>> This can lead to unpredictable results for diffrent programming
>> languages, that use diffrent ways to encode time.
>> My suggestion is here, that when a Mailbox has never been touched, the
>> SOAP interface should reply with 1970-01-01T00:00:00Z for
>> GetTimeStamp.
>> And the documentation should state this as the earliest possible
>> value.
>>
>> Thanks
>>
>> Rainer
>>
>>
>> Preston Stephenson schrieb:
>> > Internally we store times as the number of seconds since Jan 1,

>> 1970.
>> > If the string time can be converted to 0 seconds, then I have a test
>> > for the seconds being 0.
>> >
>> > Preston
>> >
>> >>>> On Thursday, March 27, 2008 at 6:08 AM, Rainer
>> > Backes<rbackesno@spambond.de>
>> > wrote:
>> >> So you simply changed the code to set any time before
>> >> 1970-01-01T00:00:00Z to 0 instead of ignoring the request ?
>> >> So GroupWise works internaly with Unix-like times ?
>> >>
>> >> Thanks
>> >>
>> >> Rainer
>> >>
>> >>
>> >> Preston Stephenson schrieb:
>> >>> I put the fix to Bonsai.
>> >>>
>> >>> With the fix, the trick is to get the value to 0.
>> >>> I've attached what java and .NET do.
>> >>> reset.cs is the code in C#.
>> >>> reset.java is the code in Java.
>> >>> reset.xml is the SOAP trace of the Java code.
>> >>> reset_ms.xml is the SOAP trace of the C# code.
>> >>>
>> >>> reset.cs:
>> >>> private void miTestItem_Click(object sender, EventArgs e)
>> >>> {
>> >>> System.DateTime date = new DateTime(0);
>> >>>
>> >>> WebReference.setTimestampRequest req = new
>> >>> vcsClient.WebReference.setTimestampRequest();
>> >>> req.backup = date;
>> >>> req.backupSpecified = true;
>> >>> req.retention = date;
>> >>> req.retentionSpecified = true;
>> >>> ws.setTimestampRequest(req);
>> >>> }
>> >>>
>> >>> reset.java:
>> >>> public void testReset() {
>> >>> Calendar cDate = Calendar.getInstance();
>> >>> cDate.setTimeInMillis( 0 );
>> >>>
>> >>> try {
>> >>> m_main.getService().setTimestampRequest( cDate, cDate,
>> >>> m_main.getSessionId(),
>> > m_main.getTrace()
>> >>> );
>> >>> }
>> >>> catch ( Exception e ) {
>> >>> e.printStackTrace();
>> >>> }
>> >>> }
>> >>>
>> >>> reset.xml:
>> >>> <?xml version="1.0" encoding="UTF-8"?>
>> >>> <env:Envelope
>> >>> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
>> >>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> >>> xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
>> >>> xmlns:ns0="http://schemas.novell.com/2005/01/GroupWise/methods">
>> >>> <env:Header>
>> >>> <ans1:session
>> >>>
>> >

>>

xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">rCxXdJSKpexgv

>> >
>> >>> BgL</ans1:session>
>> >>> <ans1:gwTrace
>> >>>
>> >

>>

xmlns:ans1="http://schemas.novell.com/2005/01/GroupWise/types">false</ans1:g

>> >
>> >>> wTrace>
>> >>> </env:Header>
>> >>> <env:Body>
>> >>> <ns0:setTimestampRequest>
>> >>> <ns0:backup>1969-12-31T17:00:00.000-07:00</ns0:backup>
>> >>> <ns0:retention>1969-12-31T17:00:00.000-07:00</ns0:retention>
>> >>> </ns0:setTimestampRequest>
>> >>> </env:Body>
>> >>> </env:Envelope>
>> >>>
>> >>> reset_ms.xml:
>> >>> <?xml version="1.0" encoding="utf-8"?>
>> >>> <soap:Envelope
>> >>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> >>> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> >>> <soap:Header>
>> >>> <session
>> >>>
>> >

>>

xmlns="http://schemas.novell.com/2005/01/GroupWise/types">e5Ypcx1c9xWOPtvg</

>> >
>> >>> session>
>> >>> </soap:Header>
>> >>> <soap:Body>
>> >>> <setTimestampRequest
>> >>> xmlns="http://schemas.novell.com/2005/01/GroupWise/methods">
>> >>> <backup>0001-01-01T00:00:00</backup>
>> >>> <retention>0001-01-01T00:00:00</retention>
>> >>> </setTimestampRequest>
>> >>> </soap:Body>
>> >>> </soap:Envelope>
>> >>>
>> >>> Sorry, I had to put the attachments inline.
>> >>> Let me know if you have questions.
>> >>>
>> >>> Preston
>> >>>
>> >>>>>> On Friday, February 08, 2008 at 5:16 AM, Preston
>> >>> Stephenson<PStephenson@gw.novell.com> wrote:
>> >>>> I'll entry a bug to look at the problem.
>> >>>> Thanks.
>> >>>> Preston
>> >>>>
>> >>>>>>> On Friday, February 08, 2008 at 4:08 AM, Rainer
>> >>>> Backes<rbackesno@spambond.de>
>> >>>> wrote:
>> >>>>> Hi,
>> >>>>>
>> >>>>> I'm working much with the SetTimeStamp request. (Archiving App.

>> !!)
>> >>>>>
>> >>>>> Now I would like to have a way to completely reset the timestamp

>> (as if
>> >
>> >>>>> I never had set it - like a new Mailbox). When I do a

>> GetTimestamp on a
>> >
>> >>>>> new Mailbox I get back 000000000T00000000Z (or similar).
>> >>>>> I have found out that the earliest time I can set is

>> 19700101T000001Z
>> >>>>> any timestamp before is ignored and not set although the Status

>> of the
>> >
>> >>>>> request came back as OK.
>> >>>>> So, What value do I have to send to completely reset the

>> timestamp
>> >>>>> (restore the 'virgin' state) ?
>> >>>>>
>> >>>>> Thanks in advance
>> >

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.