Asankha, Since you added the second init method, WDYT about this issue?
Andreas On Tue, Jan 20, 2009 at 07:14, indika kumara <[email protected]> wrote: > Hi Andreas > > When calling void init (SynapseEnvironment se), ConfigurationContext > is still in building state. I am not sure how this affects a mediator > that needs some information from ConfigurationContext in the > initialization. It may be able to move logic inside init > (ConfigurationContext cc) to init (SynapseEnvironment se) and remove > without init (ConfigurationContext cc) any issues … > BTW, these are two separate milestones in the mediator life cycle, so > separating those may have sense. > > Thanks > Indika > > On Tue, Jan 20, 2009 at 2:54 AM, Andreas Veithen > <[email protected]> wrote: >> All, >> >> I noticed that we have two different init methods for Synapse mediators: >> >> - One is defined by the optional ManagedLifecycle interface with the >> following signature: >> >> void init(SynapseEnvironment se) >> >> - The other is defined by AbstractMediator with the following signature: >> >> void init(ConfigurationContext cc) >> >> Is there any particular reason for this? It should be noted that the >> ConfigurationContext can be obtained from the SynapseEnvironment by >> casting it to Axis2SynapseEnvironment. Therefore I think that the >> second method should be eliminated. WDYT? >> >> Andreas >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
