tuscany-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Laws (JIRA)" <...@tuscany.apache.org>
Subject [jira] Assigned: (TUSCANY-3604) Fixes to make BWS_2007 work - WSDL resolution fault
Date Tue, 06 Jul 2010 15:55:50 GMT

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

Simon Laws reassigned TUSCANY-3604:

    Assignee: Simon Laws

> Fixes to make BWS_2007 work - WSDL resolution fault
> ---------------------------------------------------
>                 Key: TUSCANY-3604
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3604
>             Project: Tuscany
>          Issue Type: Bug
>          Components: OASIS Compliance - TUSCANY
>    Affects Versions: Java-SCA-2.0-M5
>         Environment: All
>            Reporter: Simon Laws
>            Assignee: Simon Laws
>             Fix For: Java-SCA-2.0
> BWS_2007  refers to multiple wsdl files in the same namespace (http://test.sca.oasisopen.org/)
but which appear in multiple contributions, e.g. 
> BWS_2007
>    Service1InvalidPort.wsdl
> BWS_General 
>    Service1.wsdl
> In this particular test the composite file explicitly refers to a service that's defined
in Service1InvalidPort.wsdl. However the OASIS SCA resolution mechanism says that, via import/export,
the runtime should look at the wsdl in BWS_General first. Tuscany does this, finds a wsdl
in the right namespace and considers the resolution complete. It them fails when it's unable
to find the service. It should continue then and look in other places rather than stopping,
i.e it should look in any other contributions that export the same namespace and then in the
local contribution. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message