Using JAXWS handlers would work, but it's probably going to have a performance drop due to requiring the SAAJ model and such to be built up.

There is a section in our FAQ related to headers:
http://cxf.apache.org/faq.html#FAQ-HowcanIaddsoapheaderstotherequest%252Fresponse%253F

That may be applicable if using the JAXWS frontend. In that case, an interceptor or invoker wouldn't be needed at all.

Dan


On Jul 29, 2008, at 11:58 PM, Gerson Galang wrote:

Thanks Glen,

I'll try your suggestion. It looks like it's going to work.

Cheers,
Gerson

On Wed, Jul 30, 2008 at 2:31 AM, Glen Mazza <[EMAIL PROTECTED]> wrote:


I believe JAX-WS handlers (analogous to interceptors but also compatible
with
Metro) along with SAAJ are good for working with SOAP Headers. There is a MessageContext within the JAX-WS handlers that will allow you to pass off data to the service implementation bean that ultimately handles the SOAP request. I have not done this before, but here is information I collected
on this topic:

http://www.jroller.com/gmazza/date/20080107
http://www.jroller.com/gmazza/date/20080204

HTH,
Glen


Gerson Galang wrote:

From what I've read, the invoke() method in the Handler has been replaced
by
the handleMessage() method of the Interceptor. The problem I have is how
I
could get hold of the header Element. Can you tell me the CXF equivalent
of
this XFire code?

    Element header = context.getInMessage().getHeader();


--
View this message in context:
http://www.nabble.com/xfire-to-cxf-migration-tp18706317p18716820.html
Sent from the cxf-user mailing list archive at Nabble.com.



---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog




Reply via email to