Hi David JAX-RS implementation can be configured to use but does not use it by default. For example, if JAX-RS JAXBElementProvider detects that an XMLStreamReader/Writer Factory is available on the message then it will be used to read from/write to the stream. One concrete example is the fast infoset support, with the fastinfoset CXF interceptors dealing with stax factories and with JAXBProvider using the same factories
cheers, Sergey On Thu, Nov 18, 2010 at 4:53 PM, KARR, DAVID (ATTSI) <[email protected]> wrote: > I've been working on separate efforts using CXF, one using JAX-RS in > WebLogic 10.3.3, and one using JAX-WS in WebLogic 10MP1. I've had no > real trouble with the first effort, but I've effectively given up on the > second effort. > > The JAX-WS implementation in WebLogic 10MP1 fails because of classloader > problems with the Stax API. I've followed all the advice on solving > this problem, but it just doesn't work in WL 10MP1. It's possible these > problems were fixed in WL 10.3.3 because I read about some people > implementing particular solutions and having it work, but only in > 10.3.3. > > After I reached this conclusion with the JAX-WS implementation, I > wondered why I wasn't having trouble with the JAX-RS implementation. It > could very well be because I'm using WebLogic 10.3.3, but I also noticed > that the resulting set of libraries for the JAX-RS implementation has > the "geronimo-stax-api_1.0_spec-1.0.1.jar", but not the Woodstox jar (I > only added jars that resolved issues in my implementation). Does this > mean that the JAX-RS implementation doesn't use the Stax API? >
