Hi,
I am having an interop problem with nil dates and a .NET 1.1 client. XFire version is 1.2.6
Basically, when returning a bean with a null date attribute the client is unable to deserialize it and throws an exception.
The SOAP response message shows :
<aDate xsi:type="xsd:dateTime" xsi:nil="true"/>
I understand that .NET 1.1 does not actually support nil DateTime but the application was running fine with Axis : the attribute gets deserialized to 0001-01-01 on the client side which is fine.
I looked at the SOAP message from Axis, it shows :
<aDate xsi:type="xsd:dateTime" xsi:nil="1"/>
I changed the Xfire code so that the BeanType deserializer sets xsi:nil to 1 instead of true and it worked.
After investigating the xfire source, it seems I could provide my own TypeCreator that could provide a new BeanType implementation that checks for date fields and sets it to a known value but this seems a bit hacky.
Any suggestions ? I am looking for a solution that does not involve this or setting a value to all the dates in the application.
Best Regards,
James Lewis
--------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
