Webservice date format

Question

I have used "clientgen" Ant task to generate the client library. The WSDL indicates that certain fields are of type xsd:date.
The web service client sends sends "2009-08-04T13:55:46.237-04:00".
However, the server expects "2009-08-04".
In the WSDL file, after you following all the links/referers URLs, you end up with the type definition:
<xs:simpleType name="PublicationDate">
<xs:restriction base="xs:date"/>
</xs:simpleType>
My questions are:
1. Is the client behaving correctly? The WSDL indicates this field is a "date" and NOT "dateTime". Perhaps the problem is in the "clientgen" Ant task which is not generating the client stubs/implementation correctly?
2. How can I change the manner in which the date gets formatted and passed on the SOAP body (java.util.Calendar)?
Edited by: user8651233 on Aug 5, 2009 7:15 AM

Answer 1

When trying to generate a client for your JAX-RPC web service from a schema. The schema includes
an schema datatype which is derived from a standard schema datatype by restriction. For example
<xs:simpleType name="SampleDate">
<xs:restriction base="xs:date"/>
</xs:simpleType>
When clientgen task is used, there is no custom class created to represent this schematype and the WSDL mappings map to the standard schema datatype rather than to your custom datatype. Subsequently, when the web service request is made, it too generates the request using the standard datatype rather than your custom datatype. The web service is expecting the custom datatype, so the request fails with a SOAP fault
There is a restriction on what Java data types can be automatically generated by the WebLogic ant
tasks: specifically, a schema data type is derived "by restriction of an existing simple type," it
is generated as the "equivalent Java data type of simple type."
This is the expected behavior for the JAX-RPC ant tasks, so the system is functioning as designed.
The solution is to program the appropriate class yourself. To do that, you would set up a class
which handles that element and does what it needs to do with the data in it.Then you would need to change the mappings that are automatically generated to point to your new custom class .
Once all that is in place, recompile your war file and retest. As long as everything is pointing
to the right places, the request and subsequent response should then be correct.
-Chandrasen.
Edited by: user10600598 on Aug 27, 2009 9:08 AM