cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glynn, Eoghan" <>
Subject RE: Protocol/HTTP headers...
Date Fri, 08 Sep 2006 07:37:27 GMT

Hi Dan,

I don't recall the original discussion, but the simplest apprach would
be to move the{REQUEST|RESPONS

This would be consistent with the use of keys (e.g. to indicate the
message is oneway) as opposed to explicit getters/setters on Message.

BTW we'll need another key on Message to indicate the flow direction
(inbound or outbound), so that the same interceptor implementation may
be inserted in both the in- and out- interceptor chains (as opposed to
using separate FooInInterceptor and FooOutInterceptor classes). 


> -----Original Message-----
> From: Kulp, John Daniel 
> Sent: 07 September 2006 22:08
> To:
> Subject: Protocol/HTTP headers...
> At some point (possibly before the apache lists were setup) 
> we had a discussion about the protocol headers and what to do 
> with them in context 
> with the transport/conduit discussions.   Unfortunately, I 
> don't remember the 
> outcome.   (I have this theory that being around a screaming 
> infant causes 
> brain rot.)
> Anyway, the JMS and HTTP transports currently have a 
> dependency on the JAX-WS API, mostly because they use the 
> MessageContext keys for adding the protocol 
> headers (as a Map<String, List<String>>) to the message.    
> The JAXB data 
> binding also has that issue (for the attachment handling).    
> Thus, what did 
> we decide to do there? 
> I cannot remember if its:
> 1) Add a new key to Message for those.
> 2) Add specific getter/setters and a map to Message for those
> 3) Add them to the conduit (are conduits reused or specific to one
> invocation?)
> Anyway, what are/were peoples thoughts?   I'd like to get the JAX-WS 
> dependency issues fixed, but that's a holdup.
> Thanks!
> --
> J. Daniel Kulp
> Principal Engineer
> P: 781-902-8727    C: 508-380-7194   F:781-902-8001

View raw message