Asankha C. Perera wrote:
Well, it is possible to keep this out of synapse of course, if synapse
doesn't want it.
As Sanjiva suggested, it could be a separate maven module or outside of
Synapse. I would slightly prefer the latter because I think it would not
be useful for a general Synapse insta
Hi Ruwan
I agree completely about making the core of Synapse OSGi
dependent. I
think the design I proposed avoids that.
Cool.. I think Ruwan's reply on an OSGi based mediator finder
would be then outside of the codebase of Synapse?
Well, it is possib
Hi Asankha,
On Tue, Dec 2, 2008 at 10:17 PM, Asankha C. Perera <[EMAIL PROTECTED]>wrote:
> Hi Paul
>
>> I agree completely about making the core of Synapse OSGi dependent. I
>> think the design I proposed avoids that.
>>
>>
> Cool.. I think Ruwan's reply on an OSGi based mediator finder would be
Paul,
The code that implements the JDK-style provider lookup is already part
of Synpase; see ExtensionDeployer#getProviders. You can recycle this
code. The only change that will be required is to replace the call to
findResource by findResources or getResources (depending on whether it
is used by
Asankha C. Perera wrote:
Hi Paul
I agree completely about making the core of Synapse OSGi dependent. I
think the design I proposed avoids that.
Cool.. I think Ruwan's reply on an OSGi based mediator finder would be
then outside of the codebase of Synapse?
I don't see any issue with that be
Hi Paul
I agree completely about making the core of Synapse OSGi dependent. I
think the design I proposed avoids that.
Cool.. I think Ruwan's reply on an OSGi based mediator finder would be
then outside of the codebase of Synapse?
My approach is to create a plugpoint which replaces the use o
Asankha
Thanks for the feedback.
I agree completely about making the core of Synapse OSGi dependent. I
think the design I proposed avoids that.
My approach is to create a plugpoint which replaces the use of
sun.misc.Service and creates a standard way of looking up available
implementations of a
Hi Ruwan/Paul
The Java ServiceProvider API [1] is now in the JDK 1.6 as the
java.util.ServiceLoader [3]
Other alternatives/workarounds for previous JDK's are the following:
Apache Commons Discovery [2]
The use of javax.imageio.spi.ServiceRegistry [4] - which though
[very] ugly was alrea
+1 for the proposal
and the OSGi Services and the Service listeners will make it very easy to
pick the mediators using OSGi.
So if we can make an OSGi based mediator finder then we can easily declare
the MediatorFactory as an OSGi service interface (no code changes required
for this), and registe
