tuscany-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelvin Goodson (JIRA)" <...@tuscany.apache.org>
Subject [jira] Resolved: (TUSCANY-3020) uniqueness spec constraint of QName in definitions not enforced
Date Mon, 01 Jun 2009 10:40:07 GMT

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

Kelvin Goodson resolved TUSCANY-3020.

       Resolution: Fixed
    Fix Version/s:     (was: Java-SCA-2.0)

Seems to be fixed now as test reports ---
org.apache.tuscany.sca.contribution.processor.ContributionReadException: java.io.FileNotFoundException:
C:\Dev\sca2.x\otest\current\target\ASM_10001 (The system cannot find the file specified)
Test ASM_10001 completed successfully

> 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-Next
> Conformance statement ASM10001 of the OASIS SCA 1.1 spec says ..
> QName is unique amongst all subelements of all <definitions/> elements in the SCA
> 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 ASM_10001_TestCase reports

> 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.

View raw message