On Sat, Dec 4, 2010 at 12:57 PM, Senaka Fernando <[email protected]> wrote:
> > > On Sat, Dec 4, 2010 at 11:52 AM, Hiranya Jayathilaka <[email protected]>wrote: > >> Hi, >> >> On Sat, Dec 4, 2010 at 11:30 AM, Hiranya Jayathilaka <[email protected]>wrote: >> >>> >>> >>> On Sat, Dec 4, 2010 at 10:21 AM, Senaka Fernando <[email protected]>wrote: >>> >>>> >>>> >>>> On Sat, Dec 4, 2010 at 10:16 AM, Afkham Azeez <[email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Sat, Dec 4, 2010 at 1:10 AM, Hiranya Jayathilaka >>>>> <[email protected]>wrote: >>>>> >>>>>> >>>>>> So the setting will go into the super tenant AxisConfiguration. >>>>>> >>>>> >>>> Yes. >>>> >>>> >>>>> That doesn't allow the super tenant user to configure his own tenant >>>>>> specific discovery proxy. >>>>>> >>>>> >>>> Well, all super tenant users inherit one axis config. The super tenant >>>> has the ability to make changes @ axis2.xml. >>>> >>> >>>> >>>>> Besides other tenants should not be using any resources configured in >>>>>> the super tenant AxisConfiguration. >>>>>> >>>>> >>>> No this is not what I meant. I was asking why treat super tenant >>>> differently? If discovery proxy is defined on the AxisConfiguration, do the >>>> same for super tenant (global AxisConfig) as well as other tenants (Tenant >>>> AxisConfig). >>>> >>> >>> So there is a global AxisConfiguration and a separate super tenant >>> AxisConfiguration? >>> >> No, IIRC, Global AxisConfiguration == super tenant AxisConfiguration. > If that is not the case we have to define two parameters to support the >>> model you are proposing. Otherwise we cannot define a global discovery proxy >>> and a tenant specific discovery proxy for the super tenant. >>> >> I am also under the impression that Super Tenant lives with all global configurations, and hence, there is no need to allow super tenant to override the global settings as a tenant. Have we done it in this manner anywhere else? Thanks, Senaka. > >> And just to clarify, we are not treating the super tenant differently. The >> parameter added to carbon.xml affects all tenants including the super >> tenant. >> > > OK, that cleared the doubt. > > >> Each tenant (including the super tenant) can override this setting by >> adding a parameter to the AxisConfiguration. >> > > As discussed, do we really need a tenant specific discovery proxy? May be > we should only consider having one global discovery proxy. > > Thanks, > Senaka. > > >> If we look at the architecture we have the Carbon ServerConfiguration >> which is common to every tenant. So that is the place to put global >> settings. Then we have AxisConfiguration instances in a per tenant basis. So >> that's the place to define tenant specific settings which may override >> global settings. >> >> Thanks, >> Hiranya >> >> >>> >>> Thanks, >>> Hiranya >>> >>> >>>> >>>> >>>>> Carbon server configuration should be the place for global settings >>>>>> IMO. >>>>>> >>>>> >>>> Yes correct, but should bot have things that are expected to end up on >>>> the global AxisConfig IMO. Azeez, you might be able to provide a better >>>> explanation? >>>> >>>>> >>>>>> Thanks, >>>>>> -H- >>>>>> >>>>> >>>>> So it looks like we will have to make some changes to Carbon in order >>>>> to make this work for tenants. >>>>> >>>> >>>> Yes, seems so. >>>> >>>> Thanks, >>>> Senaka. >>>> >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> [email protected] >>>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Senaka Fernando* >>>> Associate Technical Lead & Product Manager - WSO2 G-Reg; >>>> WSO2, Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://www.linkedin.com/in/senakafernando >>>> >>>> *Lean . Enterprise . Middleware >>>> >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> https://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 >>> >> >> >> >> -- >> 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] >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Senaka Fernando* > Associate Technical Lead & Product Manager - WSO2 G-Reg; > WSO2, Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://www.linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > -- *Senaka Fernando* Associate Technical Lead & Product Manager - WSO2 G-Reg; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
