On Wed, Apr 22, 2009 at 2:42 PM, Scott Kurz <[email protected]> wrote:
> Just wanted to note that it seems that an additional burden on the
> runtime implementor to support this API is to recognize if the service
> is described by <interface.wsdl>.
>
> If so the runtime has to establish this WSDL interface on the runtime
> representation of the reference built for the proxy without having the
> data in hand from the client side (but rather only from the side of
> the service in the domain).
>
> Would be good to have some tests for this variation with something
> like the axis2 binding.sca impl for which following the exact wsdl
> interface (instead of generating one bottom up) should matter.
>
> Scott
>
Thats an interesting point.
Presumably an SCAClient impl would only be expected to talk to an SCA domain
with a similar implementation? So the Tuscany SCAClient would use the
Tuscany SCA binding to talk to a Tuscany domain, but you wouldn't be able to
use the Tuscany SCAClient to talk to a non-Tuscany domain as the SCA binding
impl could be implemented totally differently.
And also does that mean an SCACient be only able to talk to services exposed
with the SCA binding? So this:
<component name="Service1">
<implementation.java
class="org.apache.tuscany.sca.binding.jms.ServiceImpl"/>
<service name="MyService">
<binding.jms />
</service>
</component>
would not be invokeable via SCAClient as the service isn't exposed with the
SCA binding.
...ant
