Hi, Deepal, The synchronized blocks in ConfigurationContext.java are intended to maintain the integrity of the critical tables held inside ConfigurationContext, and hopefully are placed in such a way to minimize the time spent inside of synchronized blocks. It can take a few implementation design iterations to reach the right balance between having no synchronization control and maintaining the list integrity. Ann
WebSphere Development, Web Services Engine
IBM
Deepal Jayasinghe
<[EMAIL PROTECTED]
e.lk> To
"[email protected]"
01/11/2007 10:35 <[email protected]>
PM cc
Subject
Please respond to [Fwd: Re: svn commit: r495106
[EMAIL PROTECTED] [2/10] - in
e.org /webservices/axis2/trunk/java/modul
es: integration/
integration/test/org/apache/axis2/e
ngine/
integration/test/org/apache/axis2/m
tom/
kernel/src/org/apache/axis2/address
ing/
kernel/src/org/apache/axis2/client/
kernel/src...]
Hi Bill;
Do you think its a good idea to have synchronized block (specially in
hot place like ConfigurationContext) , doesn't that slow down Axis2 ?
Thanks
Deepal
[svn text for ConfigurationContext.java updates removed by Ann Robinson]



