You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Oleg Zenzin (JIRA)" <ji...@apache.org> on 2010/07/07 21:08:56 UTC

[jira] Issue Comment Edited: (AXIS2-4370) Time portion of java.util.Date is missing from SOAP response in Axis2 1.5

    [ https://issues.apache.org/jira/browse/AXIS2-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885686#action_12885686 ] 

Oleg Zenzin edited comment on AXIS2-4370 at 7/7/10 3:07 PM:
------------------------------------------------------------

Mike, All, thanks for your comments. 

Let me to highlight an issue with current approach, mentioning of it are recurring, but I think from the practical point of view it needs more attention. Both in case of Date and Calendar we have information _lost_ at the transport layer: Date loses its time, Calendar - the style ;) The argument that "the information retrievable from a Calendar is more complete than that retrievable from a Date" is hardly convincing for me as all information we have and can effectively transport is ultimately defined by xsd type. And xsd:dateTime seems to be the most capable / comprehensive. Next would be a question "Which way is the cheapest to transfer that information from / to application level?"

Please note these considerations are purely from transport layer perspective. But what is Axis2 after all?

      was (Author: olegzenzin):
    Mike, All, thanks for your comments. 

Let me to highlight an issue with current approach, mentioning of it are recurring, but I think from the practical point of view it needs more attention. Both in case of Date and Calendar we have information _lost_ on the transport layer: Date looses its time Calendar - the style ;) The argument that "the information retrievable from a Calendar is more complete than that retrievable from a Date" is hardly convincing for me as all information we have and can effectively transport is ultimately defined by xsd type. And xsd:dateTime seems most comprehensive. Next would be a question "Which way is the cheapest to transfer that information further on application level?"

I'm looking purely from transport layer point of view here. But what is Axis2 after all..
  
> Time portion of java.util.Date is missing from SOAP response in Axis2 1.5
> -------------------------------------------------------------------------
>
>                 Key: AXIS2-4370
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4370
>             Project: Axis2
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.5
>            Reporter: Pétur Runólfsson
>         Attachments: Server-1.4.1.wsdl, Server-1.5.wsdl, Server.java, services.xml
>
>
> When a method returns a java.util.Date (or an object containing a java.util.Date), only the date portion is returned in Axis2 1.5:
> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
>    <soapenv:Body>
>       <ns:getCurrentTimeResponse xmlns:ns="http://ws.apache.org/axis2">
>          <ns:return>2009-06-10</ns:return>
>       </ns:getCurrentTimeResponse>
>    </soapenv:Body>
> </soapenv:Envelope>
> In Axis2 1.4.1, the full date and time was returned:
> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
>    <soapenv:Body>
>       <ns:getCurrentTimeResponse xmlns:ns="http://ws.apache.org/axis2">
>          <ns:return>2009-06-10T16:22:22.622Z</ns:return>
>       </ns:getCurrentTimeResponse>
>    </soapenv:Body>
> </soapenv:Envelope>
> This change breaks any application that requires the time portion to function correctly.

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