[Architecture] Changes Done to Proxy Services Do Not Take Effect

[Hiranya Jayathilaka]

Hi Folks,

Currently when we update certain elements of a proxy service configuration
from the UI (Synapse configuration admin UI) those changes do not take
effect immediately. For example let's say we have a proxy service which
contains a parameter definition. If we change the parameter value that
change does not take effect internally. Similarly any changes done to
transport bindings may not take effect. This is because the deployment
interceptor comes into play while service update takes place and reloads the
previously persisted service configuration without loading the updated the
configuration.

Does anybody have any idea how to fix this problem? What if we check the
service type at deployment interceptor and skips reloading previous
configuration if the service is of type proxy service? Note that a proxy
service is a special type of an Axis2 service. They can be changed via the
UI at will and we need to support that. Hence IMO it's ok to treat them
differently in deployment interceptor.

WDYT?

Thanks
-- 
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hiranya at wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/architecture/attachments/20090907/30de599d/attachment.html>