There is one more case. With JAX-WS, the endpoint can have an Excecutor set on it. In that case, all the processing we do will be on the main thread, but right before the invoke call, a runnable will be put on the give executor which will likely make the invoke on a background thread. The main thread will wait for a response though.
Kind of an obscure case though. The TCK is likely the only one that actually uses that functionality. :-) Dan On Tuesday 18 January 2011 9:49:13 am Nordine Boussedra wrote: > Thanx for the answers. > > Freeman Fang a écrit : > > On 2011-1-18, at 下午8:49, Daniel Kulp wrote: > >> On Tuesday 18 January 2011 7:10:53 am nordine_b wrote: > >>> Sorry for the SPAM i found the answer in the mailing list. > >>> However, in the answer Daniel says that an interceptor can pause the > >>> chain > >>> and have it resume in a different thread. > >>> Except the OneWayInterceptor is there any other CXF built > >>> interceptor that > >>> have this behavior ? > >> > >> The WS-RM things with decoupled responses MAY do this, not really > >> sure. The > >> ack would be sent back on the original thread and a new thread used > >> for the > >> processing and the ack. Not 100% sure though. > > > > Yeah, decoupled endpoint used by WS-RM or WS-ADDRESSING will switch > > thread. > > > > Freeman > > > >> The OTHER time this can occur is when using continuations. The > >> request can > >> be suspended and at some point, the container will call in again. It > >> may or > >> may not use the same thread. > > Ce message est protégé par les règles relatives au secret des > correspondances. Il est donc établi à destination exclusive de son > destinataire. Celui-ci peut donc contenir des informations > confidentielles. La divulgation de ces informations est à ce titre > rigoureusement interdite. Si vous avez reçu ce message par erreur, merci > de le renvoyer à l'expéditeur dont l'adresse e-mail figure ci-dessus et de > détruire le message ainsi que toute pièce jointe. > > This message is protected by the secrecy of correspondence rules. > Therefore, this message is intended solely for the attention of the > addressee. This message may contain privileged or confidential > information, as such the disclosure of these informations is strictly > forbidden. If, by mistake, you have received this message, please return > this message to the addressser whose e-mail address is written above and > destroy this message and all files attached. -- Daniel Kulp [email protected] http://dankulp.com/blog
