axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-3001) Problem in 1.3 RC with deserialization of java.util.Date objects that are DateTime formatted.
Date Wed, 25 Jul 2007 05:54:31 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515210
] 

Amila Chinthaka Suriarachchi commented on AXIS2-3001:
-----------------------------------------------------

As I saw in the you have declared an xml element as xs:date type and 
you have received a response as 
<ax26:timeStarted>2007-07-23T13:20:46.861Z</ax26:timeStarted> 

So you have received an invalid element(according to the xml spec).

ADB serializes the Date object correctly(only date parts). please have look at with the RC2.


if you want to parse that response then you have to declare your element as
dateTime instead of date.

But you make one point here. 
Why ADB has used the Calendar to resent the dateTime while it would have used the java.util.Date?

Actually I can not give you an answer this question without going through the code and see
any side effects of using the java.util.date. I think this was there from the begining.

Please add a new jira for this as an ADB improvement.


> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message