Understanding the source code layout
The JBossWS project 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:
The WS integration stack based on Apache CXF.
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.).
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 / WildFly webservice module functions. This is sometime required when adding features over already released application server versions.
- JBossWS 5.1.0.Final is available!
- Sep 2, 2015 9:21 AM by Alessio Soldano
- One month after the beta release, JBossWS 5.1.0 is eventually final!This time, we have gone for a time-boxed release approach and limited the number o…
- JBossWS 5.0.1.Final and 5.1.0.Beta1
- Aug 6, 2015 4:13 AM by Alessio Soldano
- It's summer time, time for a break and for taking some rest... not really, as we released two new versions of JBossWS this week :-)JBossWS 5.0.1.Final…
- Migrating sources to GitHub
- Jun 26, 2015 5:45 AM by Alessio Soldano
- I've been asked multiple times why the JBossWS project sources were still hosted on a Subversion repository. I've also had to put up with the complain…
- View more jbossws