[
https://issues.apache.org/jira/browse/AXIS2-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515301
]
Sathija Pavuluri commented on AXIS2-3001:
-----------------------------------------
To illustrate it better, I am attaching a sample POJO service source and aar
file.
If you deploy the aar, and go to the auto-generated wsdl at
http://localhost:8080/axis2/services/ManService?wsdl,
you'll see that the Man object is declared as follows:
<xs:complexType name="Man">
<xs:sequence>
<xs:element minOccurs="0" name="a" type="xs:int"/>
<xs:element minOccurs="0" name="address" nillable="true"
type="ax21:Address"/>
<xs:element minOccurs="0" name="dob" nillable="true" type="xs:dateTime"/>
<xs:element minOccurs="0" name="men" nillable="true" type="xs:anyType"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="temp" nillable="true"
type="ax21:Address"/>
</xs:sequence>
</xs:complexType>
See how, the date field dob is shown as "xs:dateTime".
However, in my Man object (which you can see in the pojosrc.zip) I had dob
declared as a java.util.Date object
And when you invoke this service (I have a test class included in the
pojosrc.zip that you can use), the response has
<dob>2007-07-23T17:27:48.017Z</dob>
So now we have this, the auto generated wsdl declares my java.util.Date object
as xs:dateTime and serializes it with both date and time parts.
I think up to that point everything is right.
But when deserializing it, it doesnt like the time part.
I think it should take into account the time part too when deserializing a
java.util.Date object.
> Problem in 1.3 RC with deserialization of java.util.Date objects that are
> DateTime formatted.
> ---------------------------------------------------------------------------------------------
>
> Key: AXIS2-3001
> URL: https://issues.apache.org/jira/browse/AXIS2-3001
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.3
> Environment: Axis 1.3 RC2, JDK 1.6 on Linux
> Reporter: Sathija Pavuluri
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Fix For: 1.3
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
