Hi Raj
Given the above situation it seems to me from architectural consistency
it would be desirable not to rely on Axis2 custom Deployer but rather
extend Synapse registry functionality to include dynamic proxy
configuration loading/ unloading. I am thinking there was a good reason
why the Synapse stopped short of loading proxy configurations from the
registry to begin with. If so I am curious.
You are right.. We first introduced dynamic sequences, then endpoints
[1] around mid-2006 but never implemented the support for dynamic
proxies because you cannot let services just appear and disappear on a
cache timeout.. Looking back, I think the dynamic nature is good - but
only when its "controlled" - i.e. I do not like the idea of endpoints,
sequences and/or proxy services coming up and dying out at will. This is
important for control, as well as reporting and management. If we expose
say a JMX method that would refresh proxy services, sequences, endpoints
etc off well known or configured registry paths etc I think that would
solve the problem - since a human is in control, and not a cache timeout
which would drive the configuration.
Please see http://markmail.org/message/iuhojtnx45ss5fuy for some
concerns with the existing dynamic nature
cheers
asankha
[1] http://markmail.org/message/zqhld3vf4gqhplpe
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
