... or rather ... How do I make JBoss 7 use Sun Metro instead of CXF ?
The only trace I found on the internet about this was this:
Which states this:
--- START ---
declaration from both
The reason is these API jars contain some classloading hacks that are trying to lookup JBossAS specific JAXWS & SAAJ impls.
If you'll remove this org.jboss.modules dependency, the hack will become disabled.
Next U'll need to extend
to include Sun RI JAXWS & SAAJ impl packages, plus define SAAJ Sun RI services & JAXWS Sun RI services in
Finally U'll need to add
dependency to both
This way Sun RI impl classes should be used from any deployment that is depending on these modules.
Removing org.jboss.modules from the two xml files, and adding sun.jdk as a dependency is easy.
Then the mystery part. Adding "something" to sun.jdk.
I figure this: javax.xml.ws
I'm adding this to my war/WEB-INF/lib:
In my web-service test method, I'm deliberately throwing an exception, to see if the stacktrace reveals that I came there through metro and not through cxf.
This did not work, because even though I made the above change, cxf remained fully functional.
It's been weeks now to get stuff working. Compiling CXF from doesn't work, JBoss 7.1.1 and 7.1.2 having too old CXFs, 7.2.0 nightly build has other changes and is a "nightly" and not "QA'ed".
CXF 2.6.1 MEX not working.
ps. I'm using 7.2.0.Final-SHAPSHOT from August 22.
So. Does anyone know how I can make JBoss 7 use Metro instead of CXF for web-services?
I'm literally at my wits' end with this whole web-services (need WS-Trust) thing. I can't / don't want to, use CXF, I need to / want to use Metro. Is this possible?