Details
Description
This bug was introduced after the fix that was made for jira AXIS2-2701.
I had originally written my comment against 2701 but since the bug is marked as resolved, thought this new issue should be tracked separately.
The fix for AXIS2-2701 makes it impossible for java.util.Date objects to be deserialized when the date is datetime formatted (i.e. yyyy-mm-dd hh:mm:ss).
It now only works for date format objects (i.e. yyyy-mm-dd)
For example I have an object with attribute:
java.util.Date timeStarted;
The element in the response looks like this:
<ax26:timeStarted>2007-07-23T13:20:46.861Z</ax26:timeStarted>
The deserialization of this element fails with this exception:
java.lang.RuntimeException: In valid string sufix
at org.apache.axis2.databinding.utils.ConverterUtil.convertToDate(ConverterUtil.java:378)
at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.makeDate(SimpleTypeMapper.java:304)
at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.getSimpleTypeObject(SimpleTypeMapper.java:117)
at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:364)
at org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:644)
at org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:592)
at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:528)
Looking at the code, it seems like the ConverterUtil expects the Date object to be only of yyyy-mm-dd format.
It fails in the case when Date is yyyy-mm-dd hh:mm:ss formatted?
Thanks,
Sathija.
Attachments
Attachments
Issue Links
- is related to
-
AXIS2-2701 Problem with ADBBean generated with WSDL2Java and Date type
- Resolved