Binding uri is built incorrectly when the target attribute is used across
deployable composites
-----------------------------------------------------------------------------------------------
Key: TUSCANY-3179
URL: https://issues.apache.org/jira/browse/TUSCANY-3179
Project: Tuscany
Issue Type: Bug
Components: Java SCA ATOM Binding Extension
Reporter: Kaushik Mukherjee
If the two components below are in different deployable composites the binding
URI is not resolved correctly in the front end. In AtomBindingInvoker the uri
formed looks like the web service uri:
http://kmukherj.dyn.webahead.ibm.com:9080/SDONewsServiceComponent/NewsService
instead of..
http://kmukherj.dyn.webahead.ibm.com:9080/sdoNewsService
<component name="FrontEndNewsComponent">
<implementation.java class="test.abdera.NewsImpl"/>
<service name="NewsClient">
<interface.java interface="test.abdera.NewsClient"/>
</service>
<reference name="newsServiceRef"
target="SDONewsServiceComponent/NewsService" >
<ts:binding.atom />
</reference>
</component>
<component name="SDONewsServiceComponent">
<implementation.java class="test.abdera.NewsServiceImpl"/>
<service name="NewsService">
<!--<interface.wsdl
interface="http://abdera.test/#wsdl.interface(NewsService)"/>-->
<interface.java interface="test.abdera.NewsService"/>
<ts:binding.atom uri="/sdoNewsService"/>
</service>
</component>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.