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.
- JBossWS 4.2.0.Beta1 and WS-Discovery support
- May 15, 2013 10:28 AM by Alessio Soldano
- Just in time for the first release of WildFly, I've cut the first Beta release of JBossWS 4.2 series and had it pulled into the application server.The…
- JBossWS 4.2 feature preview
- Apr 18, 2013 12:48 PM by Alessio Soldano
- This blog post is about few additions that are coming with JBossWS 4.2 release which I actually started working on due to some specific Narayana requi…
- Maven plugin for JAXWS tools, again!
- Feb 14, 2013 4:40 AM by Alessio Soldano
- Back in March 2010 I wrote about our JBossWS Maven plugin for running JAXWS tools (wsconsume and wsprovide). The plugin allows embedding tools' invoca…
- View more jbossws