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.
- Controlling Apache CXF Bus creation for JAXWS clients
- Oct 23, 2013 8:23 AM by Alessio Soldano
- JBossWS 4.2.2.Final has just been released and installed in current WildFly master.The new version comes with multiple bug fixes as well as a relevant…
- JBossWS 4.2.0.Final is available!
- Jul 29, 2013 11:50 AM by Alessio Soldano
- I'm happy to announce that JBossWS 4.2.0.Final is out!The release comes with lots of new features and bug fixes. To get an idea of the most relevant n…
- JBossWS 4.2.0.CR1 and the WS-Policy sets
- Jun 26, 2013 12:01 PM by Alessio Soldano
- Another WildFly release has just been announced... and it comes with the first 4.2.0 candidate release of JBossWS!The latest JBossWS release comes wit…
- View more jbossws