REST and SOAP Services with Apache CXF

Transcription

1 REST and SOAP Services with Apache CXF Andrei Shakirin, Talend ashakirin.blogspot.com/

2 Agenda Introduction in Apache CXF New CXF features Project using Apache CXF How CXF community works? 2

3 Background Software architect in Talend Team Committer in Apache CXF and Syncope projects Speaker for Apache and SOA conferences Member of OASIS S-Ramp Group 3

4 CXF History Apache Project since 2006 Basis: Celtix (ObjectWeb), XFire (Codehaus) 7 major versions, 58 patch releases 33 committers (17 active) Who uses CXF? Apache: Camel, ServiceMix, Syncope JBoss JAX-WS stack TomEE JAX-WS and JAX-RS stacks Talend, Fusesource, MuleSoft, WSO2 CXF Services List : Google Adwords, TomTom, 4

5 Why CXF? Alternatives: Axis 2 Metro Jersey CXF Benefits: Strong standards support SOAP & Rest services Security Streaming and performance Flexibility Large and active community 5

6 Standards Support JAX-WS 2.2, JAX-RS 1.1, 2.0 (TCK tests) Basic support: WS-I Basic Profile Metadata: WS-Policy, WSDL 1.1 Messaging: WS-Addressing, SOAP 1.1/1.2, MTOM Security: WS-Security, WS-SecurityPolicy, SAML, WS- Trust, WS-Notification, OAuth 2.0 Quality of Service: WS-ReliableMessaging 6

7 CXF Architecture 7

8 CXF Frontends 1. JAX-WS 2.2 Contract first (WSDL); code first Java; Spring; Blueprint based Untyped (Dispatch<>, Provider<>) Dynamic client 2. JAX-RS 1.1, 2.0 Contract first (WADL); code first Java; Spring; Blueprint based 8

9 Interceptors Chain 9

10 Phase Interceptors Outgoing Chain Business code (PRE/POST/_INVOKE, PRE/USER/POST/_LOGICAL) Umarshalling/Marshalling (MARSHAL) Protocol processing (PRE/USER/POST/_PROTOCOL, WRITE) Stream processing (PRE/USER/POST/STREAM) Transport (SEND) Incoming Chain Transport (RECIEVE) Stream processing (PRE/USER/POST/STREAM) Protocol processing (PRE/USER/POST/_PROTOCOL, READ) Umarshalling/Marshalling (UNMARSHAL) Business code (PRE/POST/_INVOKE, PRE/USER/POST/_LOGICAL) 10

11 Sample Interceptor public class SampleInInterceptor extends AbstractPhaseInterceptor<Message> { public AttachmentInInterceptor() { } super(phase.receive); getafter().add(someotherinterceptor.class.getname()); public void handlemessage(message message) { } // Process message } public void handlefault(message messageparam) { // Process fault } 11

12 CXF Interceptors: Configuration 1. Programmatically MyInterceptor myinterceptor = new MyInterceptor(); FooService client =... ; // created from generated JAX-WS client Client cxfclient = ClientProxy.getClient(client); cxfclient.getininterceptors().add(myinterceptor); 2. Using Spring/Blueprint configuration <jaxws:endpoint xmlns:tns=" implementor="#helloworldservice" endpointname="tns:helloworldserviceendpoint" servicename="tns:helloworldservice" address=" <jaxws:ininterceptors> <bean class="demo.interceptor.myinterceptor" /> </jaxws:ininterceptors> </jaxws:endpoint> 3. Dynamically using WS-Policy 4. Features 12

13 CXF Security Authentication (HTTP basic, UsernameToken, X500, Kerberos); WS-Trust 1.4: STS, SAML 2.0; JAAS Authorization (SimpleAuthorizingInterceptor, XACML*) Encrypt message and parts of message Sign message and message elements Timestamp message WS-SecurityPolicy: bindings, IssuedToken PKI support: XKMS service Transport level security 13

14 CXF Security: Security Token Service 14

15 CXF Security: Security Token Service (2.5.x) 15

16 CXF Security: XKMS (3.0.0) 16

17 CXF Security: XKMS 17

18 CXF Security: Rest Security Transport level security SSL OAuth 1.0, 2.0 Handled by App Server, Spring Security framework: customization XML message protection Propritary extensions: SAML based authentication Fediz project (WS-Federation Passive Requestor profile) 18

19 CXF Security: Fediz Subproject

20 CXF Deployment Standalone JEE (Servlet Container): Tomcat, JBoss, Glassfish,... JEE (JCA): JBoss, WebSphere, WebLogic,... OSGi: Equinox, ApacheFelix, Karaf Version 2.6: 1. CXF is splitted to different OSGi bundles 2. Configuration Admin: work queues, keystores, http conduits 20

21 CXF WSS4J 2.0 Certified JAX-RS 2.0 XKMS 2.0 WS-Eventing Internal refactorings and simplificationts 21

22 Custom Project: Rudi Idea: Dynamic multi-domain SOAP/Rest Services Platform for navigation and cartography purposes (military area) Team: 5 persons Terms: January 2011 Mai 2012 Methodology: Scrum Customer: IABG 22

23 Custom Project: Rudi Requirements: Dynamic service resolving based on WS-Policy SAML based federated authentication Role based authorization Message level security Custom messages compression Custom transport (SOAP over UDP) OSGi (radar devices, dynamic updates) 23

24 Dynamic Service Resolving 24

25 25

26 UDP Transport (Radio translation based) 26

27 CXF Community Getting involved Creating JIRA entries Submitting patches Participate in mailing list Improve Wiki documentation Publishing articles 27

28 CXF Community Roles User Developer (Contributor) Committer PMC Member PMC Chair ASF Member (Board Directors) 28

29 Links Apache CXF Project - CXF based Open Source ESB - CXF Security - CXF Rest - Policies, transport, XKMS 29