Hi,
1) Sure, you can start with a WSDL to create an SCA component.
For example, if you want to develop a Web Service with Tuscany, you can do
the following:
a. Develop a WSDL
b. Run JAX-WS wsimport tools to generated the Service Endpoint Interface
(SEI) and related JAXB classes
c. Write a Java component that implements the SEI
d. Configure the component service with Web Service binding (binding.ws)
To consume a Web Service:
c. Write a Java component that consumes the SEI by defining an SCA reference
d. Configure the component reference with Web Service binding (binding.ws)
To add a BPEL process:
a. Develop a WSDL and BPEL process
b. Create an SCA component with implementation.bpel
c. For partnerLinks, you can use Java components that consume or provide the
services using the JAX-WS SEI generated from the WSDL
2) Tuscany 2.x stream (trunk) has full OSGi integration including the
runtime enablement and a prototype of Distributed OSGi.
Thanks,
Raymond
From: Wolf, Chris
Sent: Thursday, July 16, 2009 7:08 AM
To: [email protected]
Subject: Re: top-down service creation / OSGi
Hello, I didn't see any way to search the list at:
http://mail-archives.apache.org/mod_mbox/tuscany-user/
So forgive potentially redundant questions. I have two:
1.) I looked at the service creation tutorial:
http://tuscany.apache.org/build-your-first-web-services-with-tuscany.html
I see this is a "bottom-up" approach using code annotations. My
question is: can we start with a WSDL
and create a service component for/with Tuscany?
2.) Is there a way to create a mix of service components that use different
versions of the same JAR dependencies?
i.e. something like OSGi?
Thanks,
Chris W.
NOTICE: If received in error, please destroy, and notify sender. Sender does
not intend to waive confidentiality or privilege. Use of this email is
prohibited when received in error. We may monitor and store emails to the
extent permitted by applicable law.
