You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Kelvin Goodson (JIRA)" <de...@tuscany.apache.org> on 2009/05/13 11:22:45 UTC
[jira] Created: (TUSCANY-3020) uniqueness spec constraint of QName
in definitions not enforced
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
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.
[jira] Updated: (TUSCANY-3020) uniqueness spec constraint of QName
in definitions not enforced
Posted by "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.
[jira] Resolved: (TUSCANY-3020) uniqueness spec constraint of QName
in definitions not enforced
Posted by "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 resolved TUSCANY-3020.
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: Java-SCA-2.0)
Java-SCA-Next
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 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 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.
[jira] Updated: (TUSCANY-3020) uniqueness spec constraint of QName
in definitions not enforced
Posted by "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:
------------------------------------
Description:
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 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)
...
was:
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)
...
Original report did not explicitly give failing TestCase
> 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 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.
[jira] Closed: (TUSCANY-3020) uniqueness spec constraint of QName
in definitions not enforced
Posted by "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 closed TUSCANY-3020.
-----------------------------------
> 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: OASIS Compliance - TUSCANY
> 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 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.
[jira] Updated: (TUSCANY-3020) uniqueness spec constraint of QName
in definitions not enforced
Posted by "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:
------------------------------------
Comment: was deleted
(was: 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 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 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.
[jira] Resolved: (TUSCANY-3020) uniqueness spec constraint of QName
in definitions not enforced
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws resolved TUSCANY-3020.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-2.0
Fix committed at revision: 802762
> 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 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.
[jira] Reopened: (TUSCANY-3020) uniqueness spec constraint of QName
in definitions not enforced
Posted by "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 reopened TUSCANY-3020:
-------------------------------------
reopening - as I hadn't spotted the "FileNotFound" detail of the exception currently being thrown
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
this doesn't fit with the issue title
> 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 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 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.