Ruwan
Though this is something really good.. I am a bit concerned as it seems
to be a JDK provider independent implementation of the Service Provider
model. The problem I see is in polling a directory for files to appear
(I am ok doing this one time during startup).. thus I think it should be
turned off by default at Synapse and we should provide the instructions
to turn it on. While off it should not poll the directory or have any
new thread started.
thanks
asankha
Ruwan Linton wrote:
Hi all,
I have done a MediatorDeployer to support hot deployment of mediators
(r575533) which basically is an Axis2 Deployer which is keeping an eye
on a specified folder and gives the control to the deploy method on
any file change of specified extensions.
I have put the folder as repository/mediators for mediator lookup and
the extension as .jar, which is configurable through the axis2.xml in
the repository/conf.
This implementation does not use the service providers concept because
it is only supported by the sun jdk. Instead I read the same file
(META-INF/services/org.apache.synapse.config.xml.MediatorFactory) in
the deployer to find the factory implementation and Class.forName that
factory, so that all the required classes will be loaded. Then the
deployer will register the factory implementation with the
MediatorFactoryFinder. Did the same for serializer as well.
If a particular jar contains several mediators then you have to
specify the factory implementations separated by line breaks in the
org.apache.synapse.config.xml.MediatorFactory file. As usual it is
required to present this file and at least one entry should be there
and Serializer is optional.
Any comments .....
Thanks,
Ruwan
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
