Scale It [https://community.jboss.org/people/meselfe] created the discussion "Re: How to set new SoapHandler for each invocation?" To view the discussion, visit: https://community.jboss.org/message/730602#730602 -------------------------------------------------------------- The problem is Im trying to figure out how to build a web service client that will be running in a web application and will be used by hundreds of threads concurrently. It must set various security aspects uniquely on every invocation. The security is more customized than what is usually set through the BindingProvider thus Im using a SoapHandler. So correct me if Im wrong: what I should do is create one Service instance and set the HandlerResolver only once? Each thread should use the same Service instance to create a Port instance confined to the thread? The SoapHandler is thus used by all threads concurrently because its bound to the Service instance? But then what about the SOAPMessageContext passed to the SoapHandler - is that unique to the thread? I would like to do something like this in the SoapHandler: public boolean handleMessage(SOAPMessageContext msgContext)  {    ...   msgContext.put(MessageContext.HTTP_REQUEST_HEADERS,Collections.singletonMap(MY_HTTP_HEADER,Collections.singletonList(resolver.getUserCredentials()))); The "resolver" above will get the users credentials from the FacesContext in a way that would unique to the thread. I have this working but is this solution correct - Is the use of the SoapHandler and SOAPMessageContext correct from a thread safety perspective? BTW where do you find this information about the SoapHandler - Ive been scouring through jsr 181,224,109 and various javadoc but theres hardly any info on the SoapHandler. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/730602#730602] Start a new discussion in JBoss Web Services at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

spyhunter99 [https://community.jboss.org/people/spyhunter99] created the discussion "Re: How to set new SoapHandler for each invocation?" To view the discussion, visit: https://community.jboss.org/message/730635#730635 -------------------------------------------------------------- Well, it's my job to know, and primarily through experimentation and testing. I've also stumbled upon that jsr too, but only after I had came to the same conclusion. The only thing that works differently than this is ASP.NET's Soap Extensions which is a totally different animal. If you are creating the client proxy object on demand from a jsp page, then once the page is done loading/executing, that object goes away, along with any handlers tied to it. The SOAP Message context of the client proxy object is unique to the instance of the client proxy object. This object can be used in multiple threads, but in your case (a jsp file) it is not. To the best of my knowledge, it's thread safe for use in a web app/jsp. FYI, adding http headers to request/response messages via handlers isn't super reliable. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/730635#730635] Start a new discussion in JBoss Web Services at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Scale It [https://community.jboss.org/people/meselfe] created the discussion "Re: How to set new SoapHandler for each invocation?" To view the discussion, visit: https://community.jboss.org/message/730731#730731 -------------------------------------------------------------- The 9.3.3 statement that different threads may be used for each handler in a handler chain is somewhat confusing. The solution I described above is based on the SoapHandler getting access to the user credentials through the FacesContext->ServletRequest which would be uniqe to the invocation of the service method. However if its a random thread that calls the SoapHandler then it may have no access to the user credentials through the ServletRequest. I have tested the solution on Weblogic where it seems to work but maybe Im just lucky it dosent use a pool of random threads? Unless my interpretation of 9.3.3 is wrong how would a SoapHandler that is not supposed to carry any state, only be set once to serve many invocations and run in a random thread ever get access to the credentials thats needed for that particular invocation? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/730731#730731] Start a new discussion in JBoss Web Services at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

spyhunter99 [https://community.jboss.org/people/spyhunter99] created the discussion "Re: How to set new SoapHandler for each invocation?" To view the discussion, visit: https://community.jboss.org/message/730800#730800 -------------------------------------------------------------- soap headers I think what you're referring to was written to more or less identify what happens at the web service, not the client for the web service. Most frameworks/containers will spawn as many as 10 or more instances of a web service in order to handle concurrent requests, this also implies that any handlers associated with the service will also be created. The jsr statement is saying that it's possible for only one instance of the handler to be created and thus serve all of the inbound service requests etc. Regardless, of how many copies of the handler that are, each invocation has its own message context which is unique to each client proxy instance. As long as you don't rely on private variables in your handler and store state information in the message context, then you're good to go -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/730800#730800] Start a new discussion in JBoss Web Services at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]