On Thu, Feb 17, 2011 at 10:50 AM, Samisa Abeysinghe <[email protected]> wrote:
> > > On Thu, Feb 17, 2011 at 9:12 AM, Sumedha Rubasinghe <[email protected]>wrote: > >> Are you suggesting something like Security Policy should always come from >> a specific registry, thus the user should be prevented from making that >> choice? > > > Yes, from governance registry in case of policies. My understanding was > such on these registries. > Configuration registry is where you store product specific configurations which need to be shared across multiple nodes in a cluster. Governance registry is where you store artifacts which are shared across the enterprise. So in case of security policies we need to be able to store it in both registry spaces. If the policy is used by a cluster of ESB instances, then it should go into the configuration registry. If the policy is used by ESB proxy services as well as services deployed in AS, then it should go into the governance registry. So IMO it is not correct to restrict where the user can store resources like policies. It is going to break our clustering story. Thanks, Hiranya > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
