I also assume that default SCA binding should be very easy to configure.
1) For the service side, a simple <binding.sca/> should be good enough. The
runtime should expose it to a prefered protocol (for example) at an endpoint
whose address can be derived from the composite/service naming system.
2) For the reference side, the URI will point to the target service by the
composite/service hierarchy.
The contract between a reference and a service with SCA default binding
should be transparent to application developers.
Thanks,
Raymond
----- Original Message -----
From: "Andrew Borley" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, August 14, 2006 1:09 PM
Subject: Re: Default SCA binding for services/references
Hi Raymond,
I think one of things that the SCA binding should do is enable interop
between the Java and C++ Tuscany runtimes, perhaps just on the local
system.
Obviously web services is one way of doing this (and probably the best, as
it also enables remote system interop) but if anyone wants to think about
using/find a more performant method I'd be interested in working on the
C++
side of things.
Cheers
Andy
On 8/14/06, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
The SCA spec has a notion of default SCA binding for services and
references
(An XML tag "binding.sca" is defined in SCDL). If I understand correctly,
it
can a vendor's choice of which protocol will be used as the deault.
What's
the tuscany position on this? Do we use "web service" as the default
binding? The only thing I can tell at this moment is that <binding.sca>
cannot be recognized by our loaders.
Thanks,
Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
