JBoss Web Services Introduction Richard Opalka JBoss Core Developer JBoss, a division of Red Hat 26-th January 2009 CZJUG

What is JBoss ● JBoss project started in 1999 by Marc Fleury ● JBoss Group, LLC was incorporated in 2001 in Atlanta, Georgia ● Is a division of Red Hat since 2006 ● A set of Java(EE) OSS projects

What is JBoss AS Versions Explained – JBoss AS J2EE 1.4 compliant. Any 1.4 and 1.5 certified jdk is supported – JBoss AS 4.2 – extended AS 4.0 with EJB 3.0 deployed by default. Any 1.5 and 1.6 certified jdk is supported – JBoss AS 5.0 – J2EE 1.5 compliant. Any 1.5 and 1.6 certified jdk is supported – J2EE compliant open source application server –

What is JBoss WS – JBoss AS webservices subproject – – Compliant with JAX-RPC, JAX-WS, JAXB, JAXR and SAAJ J2EE specifications – Provides JBossWS Native, Sun Metro and Apache CXF integration – Built on top of Web Service Framework 3.0 (WSF) – Main focus on JAX-WS only – JAX-RPC & JAXR proposed for removal (optional in J2EE 7?)

JBoss WS Release Cycle – RERO (Eric Steven Raymond – The Cathedral and the Bazaar) – Release every 8 weeks – 2 weeks feature/bug selection and analysis – 4 weeks implementation – 2 weeks QA and documentation – JBossWS always support last 3 stable AS releases (4.2.2, and currently) Preparation DevelopmentRelease QA Week 2 JIRA Freeze Week 6 Code Freeze Week 8 Release

Web Service Framework ● In 2008 JBoss WS introduced a general WSF ● Avoids costly NIH syndrome for WS-* extensions ● Allows web service stacks plugability to JBoss AS ● Supported open source web service stacks are – JBoss Native ( – Sun Metro ( – Apache CXF ( ● Each web service stack comes with its own feature set and performance characteristics ● Users have a choice of preferred WS stack

JBoss WS Overview AS-5.0AS-4.2AS-4.0 Target AS AS integration SPI Stack integration WS Stack WS-* extensions JBoss Native IL JBoss42 ILJBoss40 IL SPI & Framework JBoss NativeSun MetroApache CXF JAXWSTESTSUITEJAXWSTESTSUITE JBoss50 IL Sun Metro ILApache CXF IL ● JAX-WS focus only ● Common test suite ensures portability

JBossWS Modules Explained ● SPI – Abstraction providing integration points on both AS and stack side – Enables web service stacks plugability across target AS servers ● AS Integration – Provides SPI implementation for particular AS – Decouples AS internals and provides AS independent metadata ● Stack Integration – Provides SPI implementation for particular WS stack – Decouples WS stack internals from AS ● Framework – Provides AS and WS stack independent SPI implementations

JBossWS Native Provided Features ● JAX-WS ● JAX-RPC (maintenance) ● Attachments support with MTOM/XOP and SwA ● JMS Transport ● WS-Addressing ● WS-Security ● WS-Policy ● WS-Eventing ● WS-Reliable Messaging ● WS-BPEL

Sun Metro and Apache CXF Unlocked Features ● JAX-WS (TCK5 jaxws test suite pass on 100% for Metro integration) ● Attachments support with MTOM/XOP and SwA ● WS-Addressing ● WS-Security ● WS-Policy ● WS-Reliable Messaging ● No JAX-RPC support ● Upcoming JBossWS releases are expected to unlock more WS-* functionality

Cross Stack Tools ● JBossWS Management Console ( – Provides deployed endpoints list with simple statistics – Min, max, average and total request processing time – Last endpoint start and stop time – Request, response and fault count statistics ● Records Management System – Allows administrators to do custom web service traffic analysis – Allows administrators to see exchanged messages (jaxws endpoints only) – Highly extensible (customizable record aggregators and/or record filters) – Records include source host, destination host, invoked endpoint operation, etc. – Programmatic access via JBoss JMX or WSF SPI

Project Status ● Roadmap – J2EE 6 compliant implementation in JBossWS Native – Unlock more WS-* features from Sun Metro and Apache CXF ● What you can do – Feedback on the stacks ● JBossWS Native User Forum ● Sun Metro Integration User Forum ● Apache CXF Integration User Forum – Preferred Stack?

Q & A? Visit JBoss Core Developer