Understanding the source code layout
Starting with JBossWS-3.0, JBossWS provides a general web service integration layer. For the first time, our users have the choice to deploy one of three possible JAXWS stacks in different JBoss AS versions.
To make this possible and to properly separate concerns, the JBossWS is actually split up into the following sub-projects:
This defines the SPI of the abstraction layer between the AS target containers and the supported web service stacks.
This covers the final user jbossws public API:
This is the WS stack completely developed by JBoss in the past, which is still supported, extended and maintained.
The WS integration stack based on Apache CXF.
The WS integration stack based on Glassfish Metro.
This provides utilities and general purpose WS code meant to be used in all the supported stacks.
This provides the (JAXWS) tools utilities (ant tasks, scripts, etc.).
This is basically the stack agnostic testsuite:
Finally, in order for providing the proper WS integration into the the supported target containers, there're some small modules meant to override the AS webservice module functions. This is sometime required when adding features over already released application server versions.
- Moving towards JBossWS 5...
- Mar 24, 2015 12:29 PM by Alessio Soldano
- Even if I've been silent here lately, my team is actively working on JBossWS 5 and we're getting closer to the first non-Beta release.The first Beta r…
- A book on JAX-WS in WildFly and more...
- Sep 23, 2014 8:37 AM by Alessio Soldano
- It was last winter when I was offered to author a book on the Web Services stack provided by JBossWS / Apache CXF in WildFly. I eventually took up the…
- How to kick start a WS project in few seconds
- Sep 16, 2014 9:17 AM by Alessio Soldano
- One of the goals I committed to when I joined the JBoss Web Services project back in 2007 was to improve the JBossWS tooling offer and possibly make t…
- View more jbossws