Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • use JBoss AS as if it was a servlet container with no WS functionalities: this basically implies disabling the webservices subsystem for the user deployment, hence preventing the AS webservices stack from processing the ws endpoint deployment and letting the CXF libs included in the archive deal with any WS invocations when CXFServlet is hit; the webservices subsystem is turned off by adding a jboss-deployment-descriptorstructure.xml as follows to the ws endpoint deployment:
    Code Block
    xml
    xml
    <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
        <deployment>
            <exclude-subsystems>
                <subsystem name="webservices" />
            </exclude-subsystems>
        </deployment>
    </jboss-deployment-structure>
    
    this approach offers the fastest route to deploying CXF apps on JBoss AS; the drawback is that no special ws integration with JBoss AS internals is available

...