[
https://issues.apache.org/jira/browse/TUSCANY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919849#action_12919849
]
Scott Kurz commented on TUSCANY-3709:
-------------------------------------
Simon, I was trying to look at the tests before asking my question, but let me
just ask.
Are you saying that the contribution scope is being polluted with XSD
definitions or is it truly a "global" testbucket-scope that's being polluted?
My point being that I'd always assumed that an schema definition inline to a
WSDL was not hidden or further-scoped in any way simply because it was inline.
Just want to be sure you aren't arguing that point in which case I'd hope to
discuss further (I don't see the spec clarifying this, do you?).
Scott
> XSD defined in WSDL is leaking out into global scope
> ----------------------------------------------------
>
> Key: TUSCANY-3709
> URL: https://issues.apache.org/jira/browse/TUSCANY-3709
> Project: Tuscany
> Issue Type: Bug
> Components: OASIS Compliance - TUSCANY
> Affects Versions: Java-SCA-2.0-M5
> Environment: All
> Reporter: Simon Laws
>
> The otests define many WSDL and some of then re-define the same XSD elements
> in different ways. This causes Tuscany problems as we aggregate WSDL together
> and hence sometimes, depending on which way the wind's blowing, we pick up
> the the wrong schema.
> This is evident in the following tests.
> Failed tests:
> testDummy(client.ASM_12007_TestCase) *
> testDummy(client.ASM_5016_TestCase)
> testDummy(client.ASM_6004_TestCase)
> testDummy(client.ASM_6007_TestCase)
> testDummy(client.ASM_12008_TestCase) *
> testDummy(client.ASM_6014_TestCase)
> testDummy(client.ASM_6008_TestCase)
> testDummy(client.ASM_6034_TestCase)
> I note that the two tests marked with * actually have incorrect expected
> error messages recorded because of this fault.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
