Web Services Framework for JBoss AS.

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.

  • https://github.com/jbossws/jbossws-spi.git



This covers the final user jbossws public API:

  • https://github.com/jbossws/jbossws-api.git



The WS integration stack based on Apache CXF.

  • https://github.com/jbossws/jbossws-cxf.git



This provides utilities and general purpose WS code meant to be used in all the supported stacks.

  • https://github.com/jbossws/jbossws-common.git



This provides the (JAXWS) tools utilities (ant tasks, scripts, etc.).

  • https://github.com/jbossws/jbossws-common-tools.git


Container integrations

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.

  • https://github.com/jbossws/jbossws-wildfly80.git
  • https://github.com/jbossws/jbossws-wildfly81.git
  • https://github.com/jbossws/jbossws-wildfly82.git
  • etc...



We use JProfiler for profiling