Hi Jarek, Do you recall this mail from a previous related discussion.
http://mail-archives.apache.org/mod_mbox/incubator-cxf-dev/200704.mbox/% [EMAIL PROTECTED] I agree that the pre-proxy approach would seem to be more logical, but there would be a thread-safety issue around how to unset request context properties that really should only apply to a *single* invocation (e.g. an application-supplied WS-A message ID), if another invocation could kick off concurrently on another thread before the initial invocation complete. /Eoghan > -----Original Message----- > From: Jarek Gawor [mailto:[EMAIL PROTECTED] > Sent: 04 May 2007 19:15 > To: [email protected] > Subject: Request/ResponseContext of JaxWsClientProxy > > Hi, > > I have noticed that the RequestContext and ResponseContext of > JaxWsClientProxy is associated with the thread and not the > instance of the proxy. My understanding is that it should be > associated with the instance but I can't find any specific > documentation on this issue in the specs. > > Thoughts? > > Jarek >
