Jakob Skovenborg [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2003 11:44 PM
To: [EMAIL PROTECTED]
Subject: RE: Axis MessageContext to the WebService
Hej Rober and Jim
Thank's a lot. I did'nt know this ThreadLocal mechanism. For other purposes,
do you know any examples how to use it.
t WebServices? Wont you
> get a
> > MessageContext belongs to another session.
> > /Jakob
> >
> > -Oprindelig meddelelse-
> > Fra: Jim Harris [mailto:[EMAIL PROTECTED]
> > Sendt: 18. august 2003 15:10
> > Til: [EMAIL PROTECTED]
>
ion.
> /Jakob
>
> -Oprindelig meddelelse-
> Fra: Jim Harris [mailto:[EMAIL PROTECTED]
> Sendt: 18. august 2003 15:10
> Til: [EMAIL PROTECTED]
> Emne: RE: Axis MessageContext to the WebService
>
>
> Jakob
>
> Usually the MessageContext is available to
rned depending the thread that invokes it.
>
> - Rob
>
>
> - Original Message -
> From: "Jakob Skovenborg" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, August 18, 2003 10:54 PM
> Subject: Re: RE: Axis MessageContext
Hej Jim
How does that work with concurrent WebServices? Wont you get a
MessageContext belongs to another session.
/Jakob
Jim Harris <[EMAIL PROTECTED]> wrote:
> Jakob
>
> Usually the MessageContext is available to a Web service
> invoked by axis
> through the static method of the MessageConte
On Mon, 18 Aug 2003, Jakob Skovenborg wrote:
> Hej Jim
> How does that work with concurrent WebServices? Wont you get a
> MessageContext belongs to another session.
> /Jakob
It uses ThreadLocal, so it returns the current MessageContext for that
Thread.
Peter
--
Peter Mount
[EMAIL PROTECTED]
h
I assume this uses a ThreadLocal internally, so that a different object is
returned depending the thread that invokes it.
- Rob
- Original Message -
From: "Jakob Skovenborg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 18, 2003 10:54 PM
> Sent: 18 August 2003 15:55
> To: [EMAIL PROTECTED]
> Subject: Re: RE: Axis MessageContext to the WebService
>
>
> Hej Jim
> How does that work with concurrent WebServices? Wont you get a
> MessageContext belongs to another session.
> /Jakob
>
> Jim Harr
Hej Jim
How does that work with concurrent WebServices? Wont you get a
MessageContext belongs to another session.
/Jakob
Jim Harris <[EMAIL PROTECTED]> wrote:
> Jakob
>
> Usually the MessageContext is available to a Web service
> invoked by axis
> through the static method of the MessageContext
Jakob
Usually the MessageContext is available to a Web service invoked by axis
through the static method of the MessageContext class as follows:
MessageContext msgContext = MessageContext.getCurrentContext();
I think that is the one...
HTH
Jim
> -Original Message-
> From: Jakob Skovenb
one: http://www.jcp.org/aboutJava/communityprocess/final/jsr053/
(see srv.2.2).
Thanks for the clarification on MessageContext...
Cory
-Original Message-
From: Wes Devauld [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 9:38 AM
To: [EMAIL PROTECTED]
Subject: Re: Axis MessageContext
Firstly I don't think there is only one instance of a servlet for all calls
to a web context. The reason all member variables are static is because it
does create several servlets. With Servlets you do have to deal with
mulitple threading issues.
Second, MessageContext.getCurrentContext does co
12 matches
Mail list logo
