[
https://issues.apache.org/jira/browse/TUSCANY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925686#action_12925686
]
Brent Daniel commented on TUSCANY-3709:
---------------------------------------
For now, I'm going to make changes so that schema types are not aggregated into
the parent facade WSDL. The local WSDL will be checked for types first before
the other documents in the facade. I think there's still room for improvement
here, but this resolves the immediate issue.
> 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
> Assignee: Brent Daniel
>
> 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.
