RE: Deserialization: NumberFormatException: Invalid date/time

[Simon Fell]

that's not a response that is valid, according to the WSDL, either the entire element should be skipped, or it should be marked as explicitly nil, e.g. <DateModified xsi:nil='true'/>   Cheers Simon From: Christian Kunert [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 13, 2005 5:00 AM To: axis-user@ws.apache.org Subject: Deserialization: NumberFormatException: Invalid date/time Hello,   i have a problem with the deserialization of a dateTime field. The WSDL defines the field as follows:   <xs:element name="DateModified" type="xs:dateTime" nillable="true" minOccurs="0" />   This field could be part of SOAP Response and it is possible that this field is not set. In this case I get a SOAP Response containing:   <DateModified />   And now to the problem. I always get a NumberFormatException: invalid dateTime during the derserialization prozess.   Any Ideas? I’m using Axis 1.2-RC but i can reproduce the problem with axis 1.2(.x). Axis 1.1 crashes with a NullPointerException     Thanks!, Christian     {http://xml.apache.org/axis/}stackTrace:java.lang.NumberFormatException: Invalid date/time       at org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:178)       at org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502)       at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)       at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171)       at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1140)       at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:238)       at org.apache.axis.message.RPCElement.getParams(RPCElement.java:386)       at org.apache.axis.client.Call.invoke(Call.java:2402)       at org.apache.axis.client.Call.invoke(Call.java:2301)       at org.apache.axis.client.Call.invoke(Call.java:1758)