Luciano:
thanks, actually in the test/bpel/helloworld-reference composite definition
you also have a component defined with a binding.ws and there to, there is
an implementation.java element. Is it required?
<!-- Simple ws-reference -->
<!--
<component name="HelloWorldService">
<implementation.java class="helloworld.HelloWorldServiceImpl"/>
<reference name="greetingsService">
<binding.ws uri="http://localhost:8085/GreetingsService"/>
</reference>
</component>
-->
Would you consider ws bindings as the preferred way to implement cross
domain composites?
JJ-
On Fri, May 16, 2008 at 12:06 AM, Luciano Resende <[EMAIL PROTECTED]>
wrote:
> Hey Jean-Jacques Dubray
>
> Let me try to respond your questions :
>
> The helloworld.composite defined in the
> itest/bpel/helloworld-reference defines a GreetingsServiceComponent
> that is implemented by a simple pojo and has its interface contract
> defined by a wsdl, in this case greetings.wsdl. This component does
> not use the binding.ws, thus is not exposed as web services.
>
> The helloworld-ws-reference does use the binding.ws to wire to the
> service exposed by the helloworld-ws-service sample.
>
> As for the ws binding, you can use it to consume services available on
> the cloud, you can see this in the demos/xml-bigbank
>
>
> On Thu, May 15, 2008 at 1:07 PM, Jean-Jacques Dubray <[EMAIL PROTECTED]>
> wrote:
> > Luciano has pointed me towards a BPEL reference sample. It was
> constructed
> > by using the HelloWord sample which "inovkes" a GreetingsService. The
> > Greeting Service is a regular web service implemented as an SCA composite
> > (similar to the hello-ws sample).
> >
> > The hello world bpel definition exposes itself a service.
> >
> > Even though GreetingsService is a plain vanilla Web Service its reference
> > definition includes an implementation.java element:
> >
> > <component name="GreetingsServiceComponent">
> > <implementation.java class="greetings.GreetingsServiceImpl" />
> >
> > <service name="GreetingsService">
> > <interface.wsdl interface="
> > http://greetings#wsdl.interface(Greetings)<http://greetings#wsdl.interface%28Greetings%29>"
> />
> > </service>
> > </component>
> >
> > this is also true for the helloworld-ws-reference sample:
> >
> > <reference name="HelloWorldService"
> > promote="HelloWorldServiceComponent/helloWorldService">
> > <interface.java interface="helloworld.HelloWorldService" />
> > <binding.ws wsdlElement="
> > http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)<http://helloworld#wsdl.port%28HelloWorldService/HelloWorldSoapPort%29>
> "/>
> > </reference>
> >
> > Why is not a WSDL enough?
> >
> > The other question is if you use a WS binding, why does the service has
> to
> > be part of the same domain as the consumers? Could they belong to two
> > different SCA domains? As a matter of fact can a composite consume a WSDL
> > reference that is not part of an SCA domain at all?
> >
> > thanks,
> >
> > --
> > Jean-Jacques Dubray
> > 425-445-4467
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>
--
Jean-Jacques Dubray
425-445-4467
