[
https://issues.apache.org/jira/browse/TUSCANY-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732504#action_12732504
]
Anbu Ponniah commented on TUSCANY-3139:
---------------------------------------
I removed the target attribute from the component reference and added to the
promoted composite reference. With that change, the test case started working.
This was independently confirmed by our tester too. Thank you.
> Reference redefinition in implementation.jee component requires targetURI in
> spite of wsdlElement specified
> -----------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3139
> URL: https://issues.apache.org/jira/browse/TUSCANY-3139
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Misc Implementation Extensions
> Affects Versions: Java-SCA-1.5
> Environment: All
> Reporter: Anbu Ponniah
> Assignee: Simon Laws
>
> In a scenario where:
> ---- composite C1 with component c1 has a service S1 over WS binding.
> ---- composite C2 in an application.composite with a JavaEE archive(ear) with
> a component c2 with implementation.ejb defining a reference to S1 over
> default binding(with a targetURI) and promoted at the composite level
> ---- composite C3 with component c3 with implementation.jee pointing to the
> above JavaEE archive and redefining the reference over binding.ws with no
> targetURI but a WS binding element similar to "<binding.ws
> wsdlElement="http://example.com#wsdl.port(MyService/MyJDBCServiceSOAP)"/> "
> fails to resolve that reference. Note that the wsdlElement value matches the
> value specified in definition of service S1.
> However, adding a targetURI to the reference redefinition makes it work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
