Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 5476 invoked from network); 18 Apr 2007 14:28:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Apr 2007 14:28:48 -0000 Received: (qmail 4485 invoked by uid 500); 18 Apr 2007 14:28:38 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 4462 invoked by uid 500); 18 Apr 2007 14:28:38 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 4444 invoked by uid 99); 18 Apr 2007 14:28:38 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Apr 2007 07:28:38 -0700 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=HTML_MESSAGE,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [213.172.193.35] (HELO mail5.rits.idcomnet.no) (213.172.193.35) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Apr 2007 07:28:28 -0700 Received: from ngmailscan.joh.no (mail.joh.no [172.25.25.194]) by mail5.rits.idcomnet.no (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id l3IES5SB007342 for ; Wed, 18 Apr 2007 16:28:05 +0200 Received: from NGDOMINO.JOH.NO ([172.25.2.127]) by ngmailscan.joh.no with InterScan Messaging Security Suite; Wed, 18 Apr 2007 16:28:11 +0200 In-Reply-To: <60708f4b0704170208i17d79861vc595eed96099ff33@mail.gmail.com> To: axis-user@ws.apache.org Subject: Ad: Re: [axis2] Calendar serialization to xsd:dateTime bug? MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006 Message-ID: From: Tore.Larsen@norgesgruppen.no Date: Wed, 18 Apr 2007 16:27:28 +0200 X-MIMETrack: Serialize by Router on J96001/Joh(Release 7.0.2|September 26, 2006) at18.04.2007 16:27:28,Serialize complete at 18.04.2007 16:27:28 Content-Type: multipart/alternative; boundary="=_alternative 004F9BE2C12572C1_=" X-imss-version: 2.046 X-imss-result: Passed X-imss-scores: Clean:98.87346 C:2 M:3 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:2 S:4 R:2 (0.0000 0.0000) X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 004F9BE2C12572C1_= Content-Type: text/plain; charset="US-ASCII" Hei Amila, I was using ADB and when I updated binaries to snapshots from 17. april the issue was solved. I recognized that dates was adjusted to GMT during serialization and converted back again in the deserialization process. Thank you for helping me! Regards from Tore "Amila Suriarachchi" 17.04.2007 11:09 Vennligst send svar til axis-user@ws.apache.org Til axis-user@ws.apache.org cc Emne Re: [axis2] Calendar serialization to xsd:dateTime bug? What is the databinding framework you use? Can you test with a nightly build or with a RC? On 4/16/07, Tore.Larsen@norgesgruppen.no wrote: Hei, I'm using Axis 1.1.1 and I see that the Calendar serializes into 2007-04-16T10:31:29.162+0200 when it should be 2007-04-16T10:31:29.162+02:00 (missing the last colon) according to XMLSchema recommandation http://www.w3.org/TR/xmlschema11-2/#dateTime . Or am I wrong here? Soap message example: 2007-04-16T10:31:29.162+0200 18364 2007-03-01T00:00:00.000+0100 ... Regards from Tore Larsen -- Amila Suriarachchi, WSO2 Inc. --=_alternative 004F9BE2C12572C1_= Content-Type: text/html; charset="US-ASCII"
Hei Amila, I was using ADB and when I updated binaries to snapshots from 17. april the issue was solved.

I recognized that dates was adjusted to GMT during serialization and converted back again in the deserialization process.

Thank you for helping me!

Regards from Tore

"Amila Suriarachchi" <amilasuriarachchi@gmail.com>

17.04.2007 11:09
Vennligst send svar til
axis-user@ws.apache.org
Til
axis-user@ws.apache.org
cc
Emne
Re: [axis2] Calendar serialization to xsd:dateTime bug?




What is the databinding framework you use?
Can you test with a nightly build or with a RC?
On 4/16/07, Tore.Larsen@norgesgruppen.no <Tore.Larsen@norgesgruppen.no> wrote:

Hei,

I'm using Axis 1.1.1 and I see that the Calendar serializes into 2007-04-16T10:31:29.162+0200 when it should be 2007-04-16T10:31:29.162+02:00 (missing the last colon) according to XMLSchema recommandation http://www.w3.org/TR/xmlschema11-2/#dateTime .  Or am I wrong here?

Soap message example:

<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ ">
       <soapenv:Header />
       <soapenv:Body>
               <ns8:hentButikkerResponse xmlns:ns8="http://webservices.norgesgruppen.no/butikkinfo/generatedtypes/responsetypes ">
                       <ns8:hentetDato>2007-04-16T10:31:29.162+0200</ns8:hentetDato>
                       <ns8:butikkInfoList>
                               <ns8:butikkInfo>
                                       <ns8:butikkLnr>18364</ns8:butikkLnr>
                                       <ns8:gyldigFraDt>2007-03-01T00:00:00.000+0100</ns8:gyldigFraDt>
                                       ...
                               </ns8:butikkInfo>
                       </ns8:butikkInfoList>
               </ns8:hentButikkerResponse>
       </soapenv:Body>
</soapenv:Envelope>

Regards from Tore Larsen




--
Amila Suriarachchi,
WSO2 Inc.

--=_alternative 004F9BE2C12572C1_=--