Hi Tammo, The endpoint configuration changes will not get propagated to the ConfigurationContext as it is only populated within the MessageContext. In SoapExternalService the config context is created using the ODE axis2 configuration file. Hence why do we need to create new configuration context objects everytime. After going through axis2 forums i came across many threads that suggest to use one ConfigContext object to create multiple ServiceClient, as creating ConfigurationContext objects are expensive.
By bringing this change, one would now see a lot of ANON services being listed under the "Process Services". What do you say. regards, sathwik On Fri, Jun 14, 2013 at 10:35 PM, Tammo van Lessen <tvanles...@gmail.com>wrote: > Hi Sathwik, > > Each Partner service can be configured differently using endpoint > configurations. I think this is the reason for that. However I can't look > at the code right now, do I might be wrong. > > Gruß / Regards > Tammo van Lessen > > (brief, cause sent from a mobile device) > > -- > Tammo van Lessen - http://www.taval.de > Am 14.06.2013 17:53 schrieb "Sathwik B P" <sathwik...@gmail.com>: > > > The instances are being created in SoapExternalService. > > > > On Fri, Jun 14, 2013 at 9:07 PM, Sathwik B P <sathwik...@gmail.com> > wrote: > > > > > Hi, > > > > > > I have come across multiple axis2 ConfigurationContext instances in > ODE. > > A > > > new configuration context gets created for every partner channel. > > > I think we can do with a single instance shared across all the partner > > > channels. > > > Any thoughts or concerns. > > > > > > regards, > > > sathwik > > > > > >
