[jira] Resolved: (TUSCANY-2113) Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames?

["Raymond Feng (JIRA)" <tu...@ws.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raymond Feng resolved TUSCANY-2113.
-----------------------------------

    Resolution: Fixed

Fixed under r650561

> Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames?
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2113
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2113
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.1
>            Reporter: Scott Kurz
>            Assignee: Raymond Feng
>             Fix For: Java-SCA-Next
>
>
> There's a problem with how the fault matching in DTI uses the private DTI.typesMatch() method.
> I don't think it should be allowing a matching type name to return 'true', i.e. indicate a successful match.
>        return matches(t1.getElementName(), t2.getElementName()) || matches(t1.getTypeName(), t2.getTypeName());
> For one, I could have two distinct fault elems of the same type.     
> In addition, also note that, if you have a fault element with anonymous type, the generated JAXB will look like:
> @XmlType(name = ""..)
> so we will build up an XMLType with typeName equal to a namespace plus a null name.    One problem with this is that there is no way to distinguish between two fault elems in the same NS, with anonymous types. 
> I haven't given this a huge amount of thought so I mention this in case anyone thinks of other issues relating to some of the points I am making.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.