[
https://issues.apache.org/jira/browse/TUSCANY-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739964#action_12739964
]
Mike Edwards commented on TUSCANY-3196:
---------------------------------------
Thanks for spotting that there were errors in the ASM_12013_TestCase - however,
they are not the ones that you have listed ;-)
2 files were formally correct, but had incorrect statements:
ASM_12013_TestCase.java
sca-contribution.xml in contribution ASM_12013
Meanwhile, there was an error in TestComposite1.composite in contribution
ASM_12013 (it contained Java artifacts when it should not have), plus 2 errors
in the Tuscany runtime which caused exceptions.
I have fixed the errors in Tuscany and in the OASIS versions of the artifacts
and raised an ISSUE against the Assembly Test Suite.
PLEASE NOTE: If you think an OASIS testcase is wrong, please check the
TestCases document to understand what the test is supposed to do:
http://www.oasis-open.org/apps/org/workgroup/sca-assembly-testing/download.php/32961/sca-assembly-1.1-testcases-cd01.pdf
...then choose the rocks to throw...
> OASIS fixes required to make ASM_12013 work
> -------------------------------------------
>
> Key: TUSCANY-3196
> URL: https://issues.apache.org/jira/browse/TUSCANY-3196
> Project: Tuscany
> Issue Type: Bug
> Reporter: ant elder
>
> OASIS test ASM_12013 tests that where a contribution contains an
> sca-contribution.xml file that violates the schema sca-contribution.xsd that
> the SCA runtime rejects the file and raises an error, however the test
> configuration ASM_12013_TestCase.java config.output[0] is not set to
> "exception"
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
