title: Use native Java SE 6 JAX-WS implementation instead of JBoss WS stack
body: <p>JBoss 6.0 Final is shipped with <a href="http://www.jboss.org/jbossws" rel="noreferrer">JBoss WS</a> (<a href="http://cxf.apache.org/" rel="noreferrer">Apache CXF</a> stack by default), I know that I can replace the default implementation with the respective JBoss WS Native or Metro versions from <a href="http://www.jboss.org/jbossws/downloads" rel="noreferrer">JBossWS downloads site</a>.</p>
  
  <p>The problem is, I've a client jar library (binaries only unfortunately) which consumes some proprietary SOAP Web Services. When I use the client API from a Web Application deployed to JBoss I'm getting a lot of intermittent SOAP Faults (tested with both Apache CXF and JBoss Native stacks).</p>
  
  <p>Since the same Web Services seems to work fine when running from a standalone jar file (with no third party JAX-WS implementations), I was thinking about disabling the JBoss WS stack in favor of the native JAX-WS RI stack provided with Java SE 6.</p>
  
  <p>I know that JBoss Metro WS stack should be close enough to what is shipped with Java SE 6, but I would really appreciate if I could go with the native Java SE version.</p>
  
  <p>So, is this feasible? Can someone point the way? </p>