[jira] [Commented] (TUSCANY-3857) unwrapping OMElementWrapperHandler can't easily tolerate both non-valid data and minOccurs="0" data

["Scott Kurz (JIRA)" <de...@tuscany.apache.org>]

    [ https://issues.apache.org/jira/browse/TUSCANY-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014033#comment-13014033 ] 

Scott Kurz commented on TUSCANY-3857:
-------------------------------------

In r1087339, I reverted the OMElementWrapperHandler behavior to keep the itest passing.

> unwrapping OMElementWrapperHandler can't easily tolerate both non-valid data and minOccurs="0" data
> ---------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3857
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3857
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Axis Binding Extension, Java SCA Databinding-SDO
>            Reporter: Scott Kurz
>            Priority: Minor
>
> In r1086760, I committed a change to OMElementWrapperHandler.getChildren so that it could handle unwrapping a wrapper with "missing" children, i.e. children with schema def of minOccurs="0" which aren't present as a child of the wrapper.
> The code we had would, after not finding a child of given QName, group the wrapper children into like-QName-elements and then allow indexing into this list of groups.  
> This would prevent the next wrapper child from matching normally in the minOccurs="0" case, so I removed that logic.
> However, now I've broken our handling of schema-invalid payloads, as seen in the module:
> testing\itest\ws\endpoint-references
> Will have to think about how to handle both cases.
> I don't recall us talking about it in awhile, but I think the handling of XSD-invalid data is a significant feature of Tuscany that we should try not to break. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira