On Thu, Feb 17, 2011 at 10:11 AM, Hiranya Jayathilaka <[email protected]>wrote:
> > > On Thu, Feb 17, 2011 at 7:11 AM, Samisa Abeysinghe <[email protected]>wrote: > >> When I try to add a secure proxy, I see on the UI that I am given the >> choice to pick the security policy from either config or governance >> registry. > > > This is the convention we have followed in all ESB UIs (mediators, > endpoints, sequences etc). We allow the user to place the resources anywhere > in the registry. > > >> >> Is this right? >> >> I thought, this is a deployment information that we do not expose to user >> (I mean even the admin user who add a proxy) >> > > What should be the right way to present this? Should we provide the single > rooted registry view which contains all 3 registry spaces? > I was under the impression that we do that, and we do the right storage behind the scenes. In any case, should not policies come from governance registry? I think the design philosophy of these separate registries are broken when we allow user to store policies in config registry? > Personally I prefer that approach, but I'm not sure whether the registry > browser popup UI supports that. > > 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 > 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
