Achieving SOA made easy with. CeltiXfire

Size: px

Start display at page:

Download "Achieving SOA made easy with. CeltiXfire"

Ella Shepherd
5 years ago
Views:

1 Achieving SOA made easy with CeltiXfire

2 Agenda Services and SOA CeltiXfire Project Architecture Components Deployment Models Building a Service with CeltiXfire Q&A

3 Services and SOA From the OASIS SOA Reference Model: Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. Services are the mechanism by which needs and capabilites are brought together. A Service includes Requester Provider One or more message exchange patterns Requester UDDI Registry SOAP WSDL Provider

4 Services and SOA SOA is a technology independent style of design Decoupled, coarse-grained components Focus on reuse, granularity, modularity, composability, componentization, and interoperablity Compliance to standards Services identification and categorization, provisioning and delivery, and monitoring and tracking Has been mapped successfully to CORBA, message oriented middleware, Web Services

5 Benefits of Service Oriented Design More flexibility ( business agility ) Reduced cost of operation through consolidation Higher quality Reduced risk, cost and complexity for development Lessen the dependencies on vendors Good service design (partitioning) will outlive middleware or implementation technology

6 ESB for SOA Enterprise Service Bus (ESB) Provides infrastructure that can be leveraged/used to implement SOA. Characterics of an ESB Uses XML as the standard communication language Supports Web Services standards Supports messaging (synchronous, asynchronous, pointto-point, publish-subscribe) Includes standards-based adapters for integration with legacy systems Includes support for service orchestration & choreography Includes intelligent, content-based routing services Provides tranformation services Many more

7 CeltiXfire Project History Celtix project initiated as open-source project on Objectweb in June 2005 under the sponsorship of IONA Technologies To provide a feature-rich, open source Java ESB runtime Celtix 1.0 released in May 2006 XFire project initiated as open-source project on codehaus 2 ½ years ago To build a next generation SOAP framework: easy-to-use, embeddable, high performance (StAX based). CeltiXfire project accepted as incubating Apache project in August 2006

8 CeltiXfire Project Goals (1) From our Apache proposal: Project CeltiXfire is a SOA infrastructure framework focused on implementation of JCP and web service standards while also providing extensibility for legacy integration Key point is the focus on standards and extensibility

9 CeltiXfire Project Goals (2) Merge of Celtix and XFire resulting in a fast, flexible, easy-to-use and embeddable SOA and WS framework Provide Enterprise QoS and features (security, management, reliability, routing, ) Offer choice of application models, incl. native JAX-WS Wider, more active, vendor-neutral community Diverse set of developers (Envoi Solutions, IONA, LogicBlaze, BEA and Red Hat) Apache License Cooperation with other open source projects Synapse, Tuscany, ServiceMix

10 CeltiXfire Project Status Initial code drop in August 2006 Including history of both projects Currently merging Celtix and XFire codebases Adopting a more message centric approach and combining the best of both projects Releasing Milestones while incubating First milestone: core functionality with proven stability First release: all features from original projects and more, migration support for existing Celtix and XFire customers In the meantime: Celtix 1.0 still available on ObjectWeb, XFire on codehaus

11 Architecture Extensibility Extensible bus Pluggable bindings and transports Interceptor-based QoS Transparently engage reliability by adding RM interceptors to the call chain Service Model Abstraction of underlying service contracts (WSDL 1.1, WSDL 2.0, Java interfaces) Configuration-by-exception All just works out-of-the-box, configuration only required to customize

12 Extensibility (1) Bus is a provider of shared resources and services to the CeltiXfire runtime Dynamic discovery of available services Deferred loading/activation of services (when needed) Examples: Binding Factory Manager, WSDL 1.1 Manager, <extension class="org.apache.cxf.bindings.bindingfactorymanagerimpl" interface="org.apache.cxf.bindings.bindingfactorymanager"/> <extension class="org.apache.cxf.bindings.soap.soapbindingfactory" deferred="true"> <namespace> <namespace> </extension>

13 Extensibility (2) Pluggability at multiple levels Frontends, transports, bindings Component (service requestor/provider) Front-end JAX-WS JavaScript/E4X Binding XML SOAP CeltiXfire Bus QOS Transport --- WS-RM, Routing, Security, Transactions, Transformations HTTP, JMS, FTP, CORBA IIOP Network

14 Extensibility Example: CORBA Binding Developed by Yoko project Incubating in Apache Initial contributions from IONA & Trifork Full IDL type support CORBA binding use-cases Expose legacy CORBA backends as Web Services Conversely, allow CORBA clients invoke WS endpoints Leverage ORB QoS

15 Standards support Java 5 pervasive usage of annotations, generics JAX-WS 2.0 sucessor to JAX-RPC annotation-driven, optional Java-first approach JAXB 2.0 much better coverage than JAX-RPC data binding SOAP 1.1 XFire merge will also give us SOAP 1.2 & MTOM WSDL support upcoming (based on Woden)

16 Components - Transports Transport APIs HTTP JMS Symmetric concept of channels abandoned in favor of client/server specific model of conduits and destinations Support for decoupled responses (only used in HTTP transport, by RM implementation) Jetty based, stand-alone HTTP server Servlet support Based on ActiveMQ Future: FTP, Colocated,?

17 Components - Bindings Message Bindings: Realised as a set of interceptors (MustUnderstandInterceptor, ReadHeadersInterceptor, SoapInInterceptor, ) associated with phases (receive, read, protocol, ) Currently supported: SOAP 1.1, XML In work: SOAP 1.2, MTOM Future: Fixed, tagged,? Data Bindings Realised as implementations of DataReader/DataWriter interfaces. Currently supported: JAXB 2.0, XMLBeans, JiBX, Castor

18 Components - Frontends JAX-WS 2.0 JAX-WS components (Endpoint, Service, BindingProvider) built on top of/wrapping generic components JAX-WS handlers executing in CeltiXfire interceptors Wrapping of CeltiXfire Message into LogicalMessageContext, SOAPMessageContext JavaScript 1, ECMAScript for XML (E4X) 2 Service implementation is annotated with JavaScript WebServiceProvider variable Script is run in Provider type Endpoint metadata and properties obtained from WebServiceProvider variable

19 Components WS-* WS-Addressing WS-RM Multi-version support - natively 2005/08, also 2004/08 for RM Fully-fledged implementation with message persistence Transparently enabled with zero application impact Keeping an eye on WS-RX group in OASIS WS-I Basic Profile 1.1

20 Components Configuration Metadata model defines a component's configurable properties Name, type, value space restrictions, default values Consumers obtain values through Configuration interface Configuration backed by Providers Hide details of underlying source/format Can be chained - consumers are unaware of which source provided the data (WSDL or Spring) Built-in support for dynamic configuration updates using e.g. JMX

21 Components - Tooling Code generators wsdl2java, java2wsdl, xsd2wsdl, wsdl2service, wsdl2soap, wsdl2xml WSDL validator Command line based tools provided OOTB Graphical tools will be based on results from the Eclipse STP Aims to provide tools, frameworks for SOA construction in 5 subprojects (Service Creation, SCA Assembly Model, SOA System, BPEL 2 Java, BPMN) An opportunity for Open Source tooling for SOA/ESB related tools to be gathered in one place

22 Deployment Models Support for deploying into Servlet Engines Tomcat Support for deploying into J2EE Appservers Geronimo, JOnAS Support for deploying into JBI container ServiceMix, OpenESB (JBI-)internal/external consumer/provider Support for running CeltiXfire inside Apache Tuscany EnablesTuscany runtime to act as standalone web service

23 Building a Service with CeltiXfire Starting from WSDL: Use wsdl2java to generate Service endpoint interface and Service class. Server side: Implement servant (inherit from generated interface and/or use annotations only), create and publish endpoint. Client side: Create service and proxy, invoke on proxy.

24 Object obj = new HelloWorldImpl(); Endpoint.publish(ADDRESS, obj); WSDL Server mainline Server Side public class HelloWorldImpl implements HelloWorld { Generated SEI public String sayhello(string message) { return "Hello@WebService(wsdlLocation to you too!"; =, targetnamespace =, ) } public interface HelloWorld { = "sayhello") public String sayhello(string message) ) <xmlns:soap=" return "Hello to you too!"; } <binding name="helloworldbinding type="tns:helloworld"> } <soap:binding > </binding> <service name="helloworldservice"> <port binding="tns:helloworldbinding" name="helloworldport"> <soap:address location=" </port> </service> Namepace of first element in binding determines binding id/factory Namepace of first element in port determines transport id/factory

25 using generated service and SEI HelloWorldService service = new HelloWorldService(); HelloWorld proxy = Service.getHelloWorldPort(); System.out.println(proxy.sayHello("JavaZone")); Client Side Generated = "HelloWorldService", targetnamespace= ) public class HelloWorldService extends Service { private final static URL WSDL_LOCATION; private final static QName SERVICE = private final static QName PORT = public HelloWorldService() { super(wsdl_location, SERVICE); } = "HelloWorldPort") public HelloWorld gethelloworldport() { return (HelloWorld)super.getPort(PORT, HelloWorld.class); } or using generated SEI only URL url = Client2.class.getResource("/HelloWorld.wsdl"); String ns = " QName servicename = new QName(ns, "HelloWorldService"); QName portname = new QName(ns, "HelloWorldPort"); Service service = Service.create(url, servicename); HelloWorld proxy = service.getport(portname, HelloWorld.class); System.out.println(proxy.sayHello("JavaZone"));

26 Getting Involved CeltiXFire Celtix XFire Mailing lists: IRC: #cxf on irc.codehaus.org Web: Mailing lists: celtix-dev, IRC: #celtix on irc.freenode.net Web: Mailing lists: dev, announce, scm, IRC: #xfire on irc.codehaus.org

27 Questions & Answers

Eclipse SOA Tooling Platform: Project Overview. An Overview of the Eclipse STP (SOA Tooling Platform) Project

Eclipse SOA Tooling Platform: Project Overview An Overview of the Eclipse STP (SOA Tooling Platform) Project 2006 by Sybase, Inc; made available under the EPL v1.0 2/10/2006 Introduction Karl Reti STP