Hi, Just an idea that came across me,
On Mon, Mar 26, 2012 at 10:19 AM, Amila Maha Arachchi <[email protected]>wrote: > > > On Mon, Mar 26, 2012 at 10:04 AM, Sameera Jayasoma <[email protected]>wrote: > >> Hi all, >> >> Can we start working on this change after the Kernel release? Seems like >> this merging is not straight forward task. It might introduce many >> complications to the products. >> > > +1 > > IMHO we should be concentrating on the kernel at the moment. For that we > need packs to test the kernel. We are almost there on providing packs for > testing the kernel functionalities. If we do this now, > > 1. We will not get packs for some more time due to build failures > 2. We are introducing an *unnecessary variable* to our kernel testing > process. This merging is something related to product releases. So I guess > we can wait until the kernel is verified. > > Thanks, > AmilaM. > >> >> Thanks, >> Sameera. >> >> On Mon, Mar 26, 2012 at 10:00 AM, Senaka Fernando <[email protected]>wrote: >> >>> >>> >>> On Mon, Mar 26, 2012 at 9:35 AM, Hiranya Jayathilaka >>> <[email protected]>wrote: >>> >>>> >>>> >>>> On Mon, Mar 26, 2012 at 9:20 AM, Selvaratnam Uthaiyashankar < >>>> [email protected]> wrote: >>>> >>>>> On Thu, Mar 22, 2012 at 10:49 PM, Senaka Fernando <[email protected]> >>>>> wrote: >>>>> > Hi Azeez, >>>>> > >>>>> > I had a look. Merging the some Services and Products is going to be >>>>> > challenging. For example, let's take Governance. The service has >>>>> several >>>>> > things that is not required in the product. To start with there are >>>>> two >>>>> > registry.xml files. Also, there are multiple features in the Service >>>>> > P2-profile that should not be available with the product. Ex:- >>>>> throttling >>>>> > agent, metering, SSO bundles etc. Unless we sort out how to scrap >>>>> these when >>>>> > building the product, this is not going to easily work. The same is >>>>> also >>>>> > applicable to the product, where there are some client libraries >>>>> that is not >>>>> > part of the service. >>>>> > >>>>> > Also, what I don't like is to introduce hacks to check whether it is >>>>> > product-mode or service-mode and do selective branching, which >>>>> duplicates >>>>> > and makes code really ugly and unorganized. So, unless we find a >>>>> better way >>>>> > to sort issues like these out, its best kept separate right now. >>>>> >>>>> Why do we have to check whether it is product-mode or service-mode? In >>>>> stratos service, tenant 0 is acting exactly as standalone product. >>>>> Other than the binary size, I don't see any issue in merging product >>>>> and services. >>>>> >>>> >>>> I think the complexity is due to the fact that we don't need some >>>> components (functionality) in the service and we don't need some components >>>> in the product. For an example for Stratos ESB, components like Synapse >>>> artifact uploader are not required. Similarly for the product, some (most) >>>> of the stratos related components are not required. Merging all these stuff >>>> together into a single package is going to bring a lot of unnecessary stuff >>>> for both the product and the service. >>>> >>> With regard of the above concern of having unwanted components for service or product, Is it possible to keep *two* *bundles.info *files and have a switching mechanism at the product start. So the admin can select which mode that a binary pack should start either as standalone or cloud version. regards, > >>> Yes, that's nearly the same situation for G-Reg, where we don't allow >>> tenant to create mounts in Stratos etc. >>> >>> Thanks, >>> Senaka. >>> >>>> >>>> Thanks, >>>> Hiranya >>>> >>>> >>>>> >>>>> Shankar >>>>> >>>>> >>>>> > >>>>> > I also do accept the fact that this might not be the case for some >>>>> other >>>>> > products. >>>>> > >>>>> > Thanks, >>>>> > Senaka. >>>>> > >>>>> > On Thu, Mar 22, 2012 at 8:05 PM, Afkham Azeez <[email protected]> >>>>> wrote: >>>>> >> >>>>> >> Have the respective product teams started looking into this? >>>>> >> >>>>> >> -- >>>>> >> Afkham Azeez >>>>> >> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>> >> Member; Apache Software Foundation; http://www.apache.org/ >>>>> >> >>>>> >> email: [email protected] cell: +94 77 3320919 >>>>> >> blog: http://blog.afkham.org >>>>> >> twitter: http://twitter.com/afkham_azeez >>>>> >> linked-in: http://lk.linkedin.com/in/afkhamazeez >>>>> >> >>>>> >> Lean . Enterprise . Middleware >>>>> >> >>>>> >> >>>>> >> _______________________________________________ >>>>> >> Dev mailing list >>>>> >> [email protected] >>>>> >> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >> >>>>> > >>>>> > >>>>> > >>>>> > -- >>>>> > Senaka Fernando >>>>> > Product Manager - WSO2 Governance Registry; >>>>> > Associate Technical Lead; 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://linkedin.com/in/senakafernando >>>>> > >>>>> > Lean . Enterprise . Middleware >>>>> > >>>>> > >>>>> > _______________________________________________ >>>>> > Dev mailing list >>>>> > [email protected] >>>>> > http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> > >>>>> >>>>> >>>>> >>>>> -- >>>>> S.Uthaiyashankar >>>>> Senior Architect >>>>> WSO2 Inc. >>>>> http://wso2.com/ - "lean . enterprise . middleware" >>>>> >>>>> Phone: +94 714897591 >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Hiranya Jayathilaka >>>> Associate Technical Lead; >>>> WSO2 Inc.; http://wso2.org >>>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>>> Blog: http://techfeast-hiranya.blogspot.com >>>> >>> >>> >>> >>> -- >>> *Senaka Fernando* >>> Product Manager - WSO2 Governance Registry; >>> Associate Technical Lead; 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://linkedin.com/in/senakafernando >>> >>> *Lean . Enterprise . Middleware >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Sameera Jayasoma >> Technical Lead and Product Manager, WSO2 Carbon >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://tech.jayasoma.org >> >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Amila Maharachchi* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
