Hi Gabo
Hi Sergey,
If you use exchange to get to one of the message properties inside the
application code then I believe you can use JAXWS WebServiceContext and
CXF JAX-RS MessageContext extension...
That is exactly the work-around I mentioned. However, it would be nice if I could reduce it to just one, i.e. Exchange. I am using
the exchange to store business specific information that needs to be accessed at multiple points.
There's no much 'cooperation' at the moment happening between JAXWS and JAXRS runtimes except that they depend a lot on the common
core runtime, but I agree it would be good to reuse the same thread-local Exchange context. I hope we will manage to improve things
in this area a bit.
Just to confirm, the context object injected would be unique per transaction, right? Regardless of how many simultaneous
transactions there are? Or would there be some additional settings I need to set?
Yes, there will be unique objects. The actual instance injected in your class
is a thread-local proxy which will
use thread-local values...
cheers, Sergey
Gabo
