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

Kelvin Goodson updated TUSCANY-3560:
------------------------------------

    Fix Version/s: Java-SCA-Next
                       (was: Java-SCA-2.0-M5)

retargetting for after 2.0-M5

> Tuscany fails with a NPE when invoking an operation on a Reference in 
> BWS_2006_TestCase from binding.ws testsuite
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3560
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3560
>             Project: Tuscany
>          Issue Type: Bug
>          Components: OASIS Compliance - TUSCANY
>    Affects Versions: Java-SCA-2.0-M4
>            Reporter: Mike Edwards
>             Fix For: Java-SCA-Next
>
>
> New testcase BWS_2006_TestCase in the binding.ws testsuite at OASIS.
> This fails with a NPE when executing an invocation of a service operation on 
> a reference.
> In TEST_BWS_2006.composite there are 3 components:
>    TEST_BWS_2006Component1
>    TEST_BWS_2006Component2
>    TEST_BWS_2006Component3
> Component1 has a reference that is configured with a <binding.ws> binding 
> that has a @wsdlElement attribute set, pointing to a WSDL service element 
> named "Service1MultiPortService".  This WSDL service element is contained in 
> Service1.wsdl in the BWS_General contribution and the WSDL service is set up 
> to have 2 WSDL Ports:
>    Service1PortA
>    Service1PortB
> ...and these ports are set up with <soap:address/> subelements, one pointing 
> to the service address for Component2, the other to the service address for 
> Component3.
> At runtime, Tuscany should choose ONE of these Ports to use for the reference 
> - and either Component2 OR Component3 must be invoked (Tuscany is free to 
> choose which...)
> However, when the invocation is made, the NPE is thrown and it seems to be 
> because there is an EPR for this reference which has a null binding 
> (binding.ws expected...).
> To reproduce this problem, run BWS_2006_TestCase from binding.ws testsuite

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

Reply via email to