tuscany-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Jacques Dubray" <jdub...@gmail.com>
Subject Web Service References
Date Thu, 15 May 2008 20:07:59 GMT
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)" />
        </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)"/>
    </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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message