+1 to init/destroy, but i also agree with Asankha we should be clear what the use cases are for this. You'd think the mediator factory should be able to do any required initialization of a mediator, so if the XxxMediator needs its init method called then the XxxMediatorFactory would make the call.

I think the problem may be that right now the MediatorFactory doesn't have access to the SynapseConfiguration, maybe instead of adding an init method to the mediator interface whats really needed is to add the SynapseConfiguration as a parameter to the createMediator method on the MediatorFactory interface. I had this problem with the BSF mediator and had to use a synchronized method getBSFEngine in the mediator instance [1] as there is no init method. However that could be avoided if the MediatorFactory had access to the SynapseConfiguration and then just pass the BSFEngine in on the mediator constructor.

   ...ant

[1] https://svn.apache.org/repos/asf/incubator/synapse/trunk/java/modules/extensions/src/org/apache/synapse/mediators/bsf/ScriptMediator.java

On 11/7/06, Paul Fremantle <[EMAIL PROTECTED] > wrote:
Should be either

init() and destroy()

or

startup() and shutdown()

I prefer init()/destroy(), but I really don't mind.

Paul

On 11/7/06, Deepal jayasinghe < [EMAIL PROTECTED]> wrote:
> Asankha C. Perera wrote:
>
> > +1 for init() and shutdown()..
> >
> how abt stratup(); and shutdown();
>
> Thanks
> Deepal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to