Hello All I would be interested to have an exemple of an application which is not SCA aware accessing a remote SCA service which is exposed as a POJO component I understood it's possible but what kind of binding will be used in this case ?
For example, how can I access the Service exposed by CalculatorServiceCompoent from a client which is not SCA aware ? Thanks Fahim 2008/10/17 Luciano Resende <[EMAIL PROTECTED]> > Just trying to add here, there was a thread about running the > calculator-distributed from different machines, please take a look > > [1] http://markmail.org/message/qlirdpi46aydoa5b > > On Thu, Oct 16, 2008 at 8:01 AM, Simon Laws <[EMAIL PROTECTED]> > wrote: > > > > > > On Thu, Oct 16, 2008 at 1:17 PM, Seamus Kerrigan (skerriga) > > <[EMAIL PROTECTED]> wrote: > >> > >> Hi, > >> > >> I'm a relative newbie to Tuscany and I have been looking at how to use > >> an SCA domain across multiple JVMs (web servers) and machine boundaries. > >> I've seen some of the nice examples that show how to add a remote > >> reference (e.g. calculator-distributed) but in all these examples the > >> Java code for each of the nodes are all on the same build path and > >> therefore the components can easily reference each others Java > >> interfaces e.g. CalculatorServiceImpl has direct access to AddService. > >> > >> However, I'm imagining that you may want to add a reference to a related > >> Tuscany component where it's code would in a separate project or even > >> source code repository. For example, what if AddService was written by > >> another team and deployed separately to a web server. How could the > >> remote component be referenced to build a composite in this case? Do I > >> still need access to the remote Java interface or else have to publish > >> the remote service via SOAP and generate client stubs? > >> > >> Thanks in advance, > >> Seamus > > > > Hi Seamus > > > > The short answer is yes. > > > > If the client side component is going to reference a (remote) component > then > > it needs to understand the target components interface. Tuscany supports > two > > mechanisms for describing a service interface, interface.java or > > interface.wsdl. So either one of these will do. > > > > If the remote service provider gives you WSDL to describe the service you > > are trying to communicate with and if you are using implementation.java > for > > the client component then you will need to generate a java interface from > > the WSDL you have been given. You need this in order to type the > reference > > inside your client component. Other programming models may not need this, > > for example, BPEL. > > > > Hope this helps. > > > > Simon > > > > > > -- > Luciano Resende > Apache Tuscany, Apache PhotArk > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> > http://lresende.blogspot.com/ >
