No, you can use a single ConfigurationContext across thread. However, if multiple thread are going to simultaneously going to change the same properties in the Config ctx, you will need to handle the synchronization yourself. This is true for server side code as well.
HTH Azeez On Mon, Dec 15, 2008 at 11:21 AM, Shehan Simen <ssi...@itree.com.au> wrote: > Hi Samera, > > So do we have to create a ConfigurationContext for each thread? Is'nt it > too much for each thread? > > > > Regards, > > Shehan > > > > *From:* Sameera Jayasoma [mailto:sameera.madus...@gmail.com] > *Sent:* 2008-12-15 15:06 > > *To:* axis-user@ws.apache.org > *Subject:* Re: thread safe axis2 client stub > > > > > > On Tue, Dec 9, 2008 at 9:50 PM, Paul French <paul.fre...@kirona.com> > wrote: > > This seems strange to me that the client stub cannot be made thread safe. > > > > After reading the below I have changed my client service to create the > client stub on each call to one of my service methods since the client stub > is not thread safe. > > > > I have no idea how inefficient this is? I have noticed that every time I > create the client stub (for each and every call) I get the message: > > > > `[INFO] Deploying module: metadataExchange - > file:/C:/downloads/axis2/axis2-1.4.1/lib/mex-1.4.1.jar > > It suggests a lot of work is going on to simply service a single web > service call. > > > you get the above message, when creating a new ConfigurationContext > instance. Creating a CC instance is a heavy operation, therefore you can > instantiate a CC instance once and use it for all subsequent calls. > > Sameera > > > > > The link below suggests some tricks you can do to make things more > efficient. What are these tricks? > > > > Thanks > > Paul > > > ------------------------------ > > *From:* Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] > > *Sent:* 09 December 2008 04:26 > > > *To:* axis-user@ws.apache.org > *Subject:* Re: thread safe axis2 client stub > > > > I was not aware of this. If the axis2 design not permits this it is better > not to use it. > > thanks, > Amila. > > On Mon, Dec 8, 2008 at 10:00 AM, Shehan Simen <ssi...@itree.com.au> wrote: > > Also this link: > > > http://markmail.org/message/iif5rdpgqahk4u5t#query:axis2%20client%20stub%20thread%20safe+page:2+mid:eenup3ck5ib6fzqq+state:results > > > > > > *From:* Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] > *Sent:* 2008-12-08 15:26 > > > *To:* axis-user@ws.apache.org > *Subject:* Re: thread safe axis2 client stub > > > > I have tested with Axis2 1.4 and it worked fine. can you please send the > mail thread you mentioned? > > thanks, > Amila. > > On Mon, Dec 8, 2008 at 9:48 AM, Shehan Simen <ssi...@itree.com.au> wrote: > > Hi Amila, > > Thank you for your response. But I found in some discussion, it is saying > that the client stub is not thread safe. Is this problem fixed now? In which > version I can find it then? > > > > Regards, > > Shehan > > > > *From:* Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] > *Sent:* 2008-12-08 15:13 > *To:* axis-user@ws.apache.org > *Subject:* Re: thread safe axis2 client stub > > > > yes > > thanks, > Amila. > > On Mon, Dec 8, 2008 at 9:31 AM, Shehan Simen <ssi...@itree.com.au> wrote: > > Hi, > > I am going to invoke a web service via a client stub generated by axis2. > > I want to have a single instance of the stub across my application. > > So when I initiate the stub (when I call the constructor), I don't like to > call it again throughout my application. > > Is it thread safe? > > > > Regards, > > Shehan > > > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > > > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > > > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > > > > > -- > Sameera > http://sameera-jayasoma.blogspot.com/ > http://www.flickr.com/photos/sameera-jayasoma > -- Thanks Afkham Azeez Blog: http://afkham.org Developer Portal: http://www.wso2.org WSAS Blog: http://wso2wsas.blogspot.com Company: http://wso2.com GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
