[ http://wso2.org/jira/browse/MASHUP-296?page=all ]
Keith Godwin Chapman resolved MASHUP-296.
-----------------------------------------
Resolution: Fixed
> Consider full support for QName datatype
> ----------------------------------------
>
> Key: MASHUP-296
> URL: http://wso2.org/jira/browse/MASHUP-296
> Project: WSO2 Mashup Server
> Issue Type: Improvement
> Reporter: Jonathan Marsh
> Assigned To: Keith Godwin Chapman
> Priority: Minor
> Fix For: 1.0
>
>
> If we find use cases supporting QName valued parameters we would need the
> following capabilities:
> 1) ability to return an E4X QName object, mapping to a lexical QName, plus a
> corresponding namespace declaration on the parameter wrapper.
> 2) ability to accept a lexical QName, plus corresponding namespace, and
> construct an E4X QName object.
> 3) ability to serialize/deserialize such XML in the E4X stubs.
> 4) ability to bind a namespace in the Try-it for a QName parameter.
> 5) a JS/DOM analogue to a QName object, perhaps a JS native version, or a
> "namespace" expando property on a string.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
