Web Service Message Properties

[jp4 <jo...@hnpsolutions.com>]

I'd like to add some functionality to all of my web service applications
(using CXF 2.2.2).  The applications are distributed into several physical
deployments.  Sometimes, it's very helpful to be able to track a single
request from one application to another.  For this reason, I'd like the
first application in the chain to generate a GUID and pass it along to all
other applications in the call stack.  

I was wondering if this is possible without modifying my contract?  I don't
think it's appropriate to advertise this to clients.  Is there a mechanism
for doing this in CXF.  One thing I should mention is that we use both HTTP
an JMS protocols, so the solution should be protocol agnostic.

Thanks,

John
-- 
View this message in context: http://www.nabble.com/Web-Service-Message-Properties-tp25998180p25998180.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: Web Service Message Properties

[Daniel Kulp <dk...@apache.org>]

You could do this either by:
1) Protocol header: HTTP and JMS both propagate the values in the 
Message.PROTOCOL_HEADER map in the message/context.   Thus, you could just set 
a protocol header and make sure all the steps along the way copy it through.

2) Soap header:   You could add a mustUnderstand=false type header to the soap 
message (see http://cxf.apache.org/faq.html) and propagate that through as 
well.

Dan


On Wed October 21 2009 2:54:05 pm jp4 wrote:
> I'd like to add some functionality to all of my web service applications
> (using CXF 2.2.2).  The applications are distributed into several physical
> deployments.  Sometimes, it's very helpful to be able to track a single
> request from one application to another.  For this reason, I'd like the
> first application in the chain to generate a GUID and pass it along to all
> other applications in the call stack.
> 
> I was wondering if this is possible without modifying my contract?  I don't
> think it's appropriate to advertise this to clients.  Is there a mechanism
> for doing this in CXF.  One thing I should mention is that we use both HTTP
> an JMS protocols, so the solution should be protocol agnostic.
> 
> Thanks,
> 
> John
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog