[
https://issues.apache.org/jira/browse/TUSCANY-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842684#action_12842684
]
Simon Laws commented on TUSCANY-3370:
-------------------------------------
There is another problem with these tests. All of the WSDL in the policy tests
is defined in the same namespace. For example,
POL_3001
import: http://test.sca.oasisopen.org/
Service1.wsdl - defined in http://test.sca.oasisopen.org/
Policy_General
export: http://test.sca.oasisopen.org/
Service1.wsdl - defined in http://test.sca.oasisopen.org/
So, during resolution, the runtime looks in the imports first and finds the
required namespace. It looks for the required WSDL binding but doesn't find it
so raises and Warning to this effect. It doesn't look in the local contribution
as it's already found the namespace being exported by another contribution.
First of all is this the right WSDL resolution process w.r.t WSDL in the same
namespace but which appear in different contributions.
> Question regarding POL_3001_TestCase and POL_3002_TestCase
> ----------------------------------------------------------
>
> Key: TUSCANY-3370
> URL: https://issues.apache.org/jira/browse/TUSCANY-3370
> Project: Tuscany
> Issue Type: Bug
> Components: OASIS Compliance - OASIS, OASIS Compliance - TUSCANY
> Affects Versions: Java-SCA-2.0
> Environment: All
> Reporter: Simon Laws
> Fix For: Java-SCA-2.0
>
>
> Both POL_3001_TestCase and POL_3002_TestCase rely on configuration of
> binding.ws with a WSDL ejb binding in order to test that the specification of
> a SOAP intent with and EJB binding is noticed as erroneous. I don't know what
> our binding.ws does with the ejb binding but at best I expect it ignores it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
