You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <tu...@ws.apache.org> on 2007/05/11 12:53:15 UTC
[jira] Created: (TUSCANY-1267) Provide a way for binding extensions
to get at the interface defined on the associated service or reference
Provide a way for binding extensions to get at the interface defined on the associated service or reference
-----------------------------------------------------------------------------------------------------------
Key: TUSCANY-1267
URL: https://issues.apache.org/jira/browse/TUSCANY-1267
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Kernel
Affects Versions: Java-SCA-0.90
Reporter: ant elder
Priority: Minor
Fix For: Java-SCA-Next
With the following:
<reference name="HelloWorldService" promote="HelloWorldServiceComponent/helloWorldService">
<interface.wsdl interface="http://helloworld#wsdl.interface(HelloWorld)" />
<binding.ws wsdlElement="http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)"/>
</reference>
it doesn't look like there is any way for the Axis2 binding or WebService binding to get at the interface.wsdl definition ascociated with the reference. A similar problem exists for <service> although it is possible to get to the interface there from one of the runtime objects.
I wondered if o.a.t.assembly.Binding could have an interfaceContract which could be set by the runtime before calling the Binding resolve method.
This would also make all the extension code which needs to mess about with binding interfaces much simpler.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Resolved: (TUSCANY-1267) Provide a way for binding
extensions to get at the interface defined on the associated service or
reference
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Sebastien Delfino resolved TUSCANY-1267.
---------------------------------------------
Resolution: Fixed
A reference binding provider is given the reference configured with the binding, from it it can get the interface contract specified on the reference.
Please reopen if this does not meet your requirement. Thanks.
> Provide a way for binding extensions to get at the interface defined on the associated service or reference
> -----------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1267
> URL: https://issues.apache.org/jira/browse/TUSCANY-1267
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-0.90
> Reporter: ant elder
> Priority: Minor
> Fix For: Java-SCA-Next
>
>
> With the following:
> <reference name="HelloWorldService" promote="HelloWorldServiceComponent/helloWorldService">
> <interface.wsdl interface="http://helloworld#wsdl.interface(HelloWorld)" />
> <binding.ws wsdlElement="http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)"/>
> </reference>
> it doesn't look like there is any way for the Axis2 binding or WebService binding to get at the interface.wsdl definition ascociated with the reference. A similar problem exists for <service> although it is possible to get to the interface there from one of the runtime objects.
> I wondered if o.a.t.assembly.Binding could have an interfaceContract which could be set by the runtime before calling the Binding resolve method.
> This would also make all the extension code which needs to mess about with binding interfaces much simpler.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org