[wsf-c-dev] [jira] Resolved: (WSFPHP-307) xsi:type based serialization and deserialization should be impelemted.
Dimuthu Gamage (JIRA)
jira at wso2.org
Tue Jul 29 01:42:52 PDT 2008
[ https://wso2.org/jira/browse/WSFPHP-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimuthu Gamage resolved WSFPHP-307.
-----------------------------------
Resolution: Fixed
Fixed.
Test cases were added.
client side test (https://wso2.org/repos/wso2/trunk/wsf/php/src/tests/samples/wsdl_mode)
ComplexTypeComplexExtensionInternalElementParentTypeClient.phpt
ComplexTypeComplexExtensionParentTypeClient.phpt
server side tests (https://wso2.org/repos/wso2/trunk/wsf/php/src/tests/samples/services/wsdl_mode)
ComplexTypeComplexExtensionInternalElementParentTypeService.php
ComplexTypeComplexExtensionParentTypeService.php
Thanks
Dimuthu
> xsi:type based serialization and deserialization should be impelemted.
> ----------------------------------------------------------------------
>
> Key: WSFPHP-307
> URL: https://wso2.org/jira/browse/WSFPHP-307
> Project: WSO2 WSF/PHP
> Issue Type: Bug
> Components: WSDL Mode
> Affects Versions: 2.0.0
> Environment: Linux + windows
> Reporter: Dimuthu Gamage
> Assignee: Dimuthu Gamage
> Fix For: 2.0.0
>
>
> This is required when a user provide sub type in place of a super type. In that case we have to serialize the message according to the user type. And in incomming message we have to deserialize looking at the xsi:type attribute of the element.
--
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 Wsf-c-dev
mailing list