You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/10/20 10:57:44 UTC

DO NOT REPLY [Bug 23928] New: - Java Date Deserialization on As400

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23928>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23928

Java Date Deserialization on As400

           Summary: Java Date Deserialization on As400
           Product: Axis
           Version: 1.1
          Platform: Other
        OS/Version: OS/400
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: aedemar.cooke@rbc.com


When .Net client invokes Axis web service method which takes an object with a 
Java Date property, the hour seems to be deserialized to an hour behind the 
date value the .NET client set.

This only happens when the .NET client accesses the application on the iSeries 
(V5R1 running WAS V4.05).  When the .NET client calls same method on same 
application running on Win2K server (running WSAD test server WebSphere 
Application Server, Advanced Developer Edition V4.0), the deserialized date 
value is the same as the original value.

- <complexType abstract="true" name="DateQuery">
- <sequence>
  <element name="startDate" nillable="true" type="xsd:dateTime" /> 
  <element name="endDate" nillable="true" type="xsd:dateTime" /> 
  </sequence>
  </complexType>