On Wed, May 7, 2014 at 1:12 PM, Gihan Anuruddha <[email protected]> wrote:
> Hi Kasun, > > No, not always. We can do changes that backward compatible way like we > did in our last BAM 2.4.1 release. Even though might need to add > improvements frequently to these client components. > > Ok. Either way, both these set of components need to live outside the carbon-commons. Regards, > Gihan > > > On Wed, May 7, 2014 at 12:59 PM, Kasun Gajasinghe <[email protected]> wrote: > >> Hi Gihan, >> >> >> On Wed, May 7, 2014 at 11:23 AM, Gihan Anuruddha <[email protected]> wrote: >> >>> Hi Rajeev, >>> >>> We can divide databridge components into a two separate parts as >>> server and client. AFAIK at the moment server part only used by BAM and >>> CEP. But I think client part might need to all other wso2 products since we >>> are going to create toolboxes for all of them. So IMHO is we can keep >>> those client components in the carbon-commons and we can create >>> separate git repo for the databridge server related components. >>> >> >> When you change the data-bridge server/receiver, you will also have to >> modify the clients appropriately, right? Therefore, I think it's better >> keep all in one place. And, I'm -1 to keep any data-bridge components in >> carbon-commons. Carbon-commons is not the place to keep components that >> changes frequently. It's for components like soap-tracer, wsdl2code etc. >> that hardly get any commit. >> >> I'm +1 to create a new repo to keep the data-bridge components. There >> around 11 data-bridge components as I see. >> >> Regards, >> KasunG >> >> >>> >>> WDYT? >>> >>> Regards, >>> Gihan >>> >>> >>> On Wed, May 7, 2014 at 10:56 AM, Rajeev Sampath <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> Currently part of the data-bridge (core components) are in >>>> carbon-commons and the rest is in carbon-analytics. However there are >>>> arguments that carbon-commons is not the right place to have these >>>> data-bridge components. >>>> >>>> Completely moving this to carbon-analytics doesn't seem to be a good >>>> option either since quite a few products depend on this and they will have >>>> to wait for a carbon-analytics release when there are updates. >>>> >>>> Do we need a separate git repo for data-bridge? Or else a better place >>>> to move this? >>>> >>>> >>>> Thanks >>>> Rajeev >>>> >>>> -- >>>> Rajeev Sampath >>>> Senior Software Engineer >>>> WSO2, Inc.; http://www.wso2.com. >>>> >>>> Mobile: >>>> * +94716265766 <%2B94716265766>* >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> W.G. Gihan Anuruddha >>> >>> Senior Software Engineer | WSO2, Inc. >>> M: +94772272595 >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> >> >> > > > > -- > W.G. Gihan Anuruddha > Senior Software Engineer | WSO2, Inc. > M: +94772272595 > -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
