[
https://issues.apache.org/jira/browse/TUSCANY-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731376#action_12731376
]
Simon Laws commented on TUSCANY-3139:
-------------------------------------
I'm concerned about some aspects of this scenario
The reference on c2 should only target components in the same composite. To set
a default for the promoted reference the target should appear on the composite
level reference. The target is validly unresolved in this case as the service
is not available in the composite that holds c2. Even if it were available the
bindings don't match.
It's odd that you don't get a reference multiplicity error. You are defining a
local target and a promoted target for a reference that has a maximum
multiplicity of 1. Maybe it's just hidden by the resolution error.
Can you try putting the target on the composite reference rather than the
component reference. This may uncover problems with the override logic but
difficult to tell at the moment.
> 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.
