synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Fremantle <>
Subject Re: MediatorFinder interface
Date Thu, 13 Oct 2005 21:06:13 GMT

I guess I was thinking that the name of a mediator in the rulelist is the
name of a *deployed* instance of a Mediator class.
SO then the MediatorFinder interface would still have a String. My real
implementation of a MediatorFinder interface that I planned was a
SpringMediatorFinder class in which the string is the name of a deployed
spring bean in a given spring context.

Other MF classes could include other models for configuring Mediators. But I
was pushing out the parameterisation job to a separate file from the

On the other hand we may want to allow variables in the xpaths.


On 10/13/05, ant elder <> wrote:
> In the code Paul put up he has a MediatorFinder interface:
> I like this, and I have similar MediatorFactory in the prototyping i'm
> doing. Its useful when creating Mediators which require more information
> than just the name, eg, XSLT or E4X scripts. You can delegate to a mediator
> specific factory to create the mediator instance based on context
> information. But, you could probably do the same type of thing in the init
> lifecycle method of a Mediator (what is the signature of that by the way?).
> What do peope think, is it worth formalizing an interface for this along
> the lines of:
> interface MediatorFactory
> Mediator createMediator(MediatorDescription md);
> }
> ...ant

View raw message