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" <[EMAIL PROTECTED]> 
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, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 
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. 

Reply via email to