On Thursday 28 October 2010 1:28:34 pm KARR, DAVID (ATTSI) wrote: > Although I've been using CXF for the JAX-RS implementation for a while, > I'm now looking at it to implement some Soap client calls. I had some > miscellaneous questions. > > Just to be sure, if I'm working contract-first and I generate the JAXB > classes and the stubs with "wsdl2java", do I have to package the WSDL > and schemas for deployment at runtime? I'll probably want to have the > option of schema validation. I thought I noticed something in the docs > that indicated if you used the "jaxws:client" Spring element, the > implication was that you didn't need the WSDL packaged at runtime.
You don't NEED the wsdl/schemas at runtime with CXF (you would with pure JAX- WS) for most usecases, but it's recommended if you can. If you do schema validation, you would need it though as we would need the original schema to validate against. > I'm going to need some special interceptors that do logging in > particular ways, so I can't use the "out of the box" logging > interceptors. This looks straightforward. > > I'm also going to need an "in" interceptor that can cause the original > service call to fail with a particular exception, instead of making the > call. This doesn't seem as straightforward. Just throw a Fault (or, more specifically, our SoapFault subclass) with whatever details filled in that you want. -- Daniel Kulp [email protected] http://dankulp.com/blog
