[jira] Updated: (TUSCANY-3020) uniqueness spec constraint of QName in definitions not enforced

["Kelvin Goodson (JIRA)" <de...@tuscany.apache.org>]

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

Kelvin Goodson updated TUSCANY-3020:
------------------------------------

    Fix Version/s: Java-SCA-2.0

> uniqueness spec constraint of QName in definitions not enforced
> ---------------------------------------------------------------
>
>                 Key: TUSCANY-3020
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3020
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA spec compliance
>            Reporter: Kelvin Goodson
>             Fix For: Java-SCA-2.0
>
>
> Conformance statement ASM10001 of the OASIS SCA 1.1 spec says ..
> QName is unique amongst all subelements of all <definitions/> elements in the SCA Domain
> but file src\main\resources\ASM_10001\META-INF\definitions.xml in the OASIS test suite has 2 intents with the same QName.
> We should fail with an exception,  but we don't.  Instead we report 
> org.junit.ComparisonFailure: expected:<[exception]> but was:<[ASM_10001 request service1 operation1 invoked]>
> 	at org.junit.Assert.assertEquals(Assert.java:123)
> 	at org.junit.Assert.assertEquals(Assert.java:145)
> 	at client.BaseJAXWSTestCase.testDummy(BaseJAXWSTestCase.java:148)
> ...

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