[mashup-dev] [jira] Resolved: (MASHUP-738) Consider dynamic type conversion on dateTime returns

Keith Godwin Chapman (JIRA) jira at wso2.org
Thu May 1 03:36:18 PDT 2008


     [ https://wso2.org/jira/browse/MASHUP-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Godwin Chapman resolved MASHUP-738.
-----------------------------------------

    Resolution: Fixed

> Consider dynamic type conversion on dateTime returns
> ----------------------------------------------------
>
>                 Key: MASHUP-738
>                 URL: https://wso2.org/jira/browse/MASHUP-738
>             Project: WSO2 Mashup Server
>          Issue Type: Improvement
>            Reporter: Jonathan Marsh
>            Assignee: Keith Godwin Chapman
>             Fix For: 1.1
>
>
> The first of these works, the second doesn't.  The stubs now variously accept a date object or an xs:dateTime compatible string when the type is declared as xs:dateTime.  Should we do something similar on the server side?  If the return value is a string, and is valid, can't we send that rather than force the user to parse it into an xs:dateTime just so we can serialize it back out?
> getDate.outputType = "xs:dateTime";
> function getDate() {
>     return (new Date());
> }
> getXsDate.outputType = "xs:dateTime";
> function getXsDate() {
>     return "2008-01-01T04:03:02Z";
> }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the Mashup-dev mailing list