> Registry in the core. But we are going to keep bare minmal things in the > kernel. For an example we going to remove all UM implementations but keep > the API and a simple file based implementation. > > OTOH I think this registry based one can not be used without UI (unless > some one creates a data source directly in registry). So better to keep UI > and registry based one in the same component. >
Well if the registry is anyway going to be there .. we can just keep it there :) .. the registry based data sources and the UI component cannot be associated . the UI component is just only the UI .. as you said .. there can be other situations where the component has to read data sources from the registry without the UI being there .. anyways we can decide on this properly later .. > > thanks, > Amila. > >> >> >>> >>> thanks, >>> Amila. >>> >>>> >>>> So then, the other issue mentioned by Amila for the data source >>>> component to be independent of Axis2, we need a common clustering component >>>> which defined an abstraction layer, where there probably can be pluggable >>>> implementations like Axis2 Tribes clustering or something based on >>>> Hazelcast and so on, so we will not bind to a specific library. I'm >>>> guessing Azeez was working on the Hazelcast based implementation, he would >>>> have more info on that. >>>> >>>> Cheers, >>>> Anjana. >>>> >>>> >>>> On Tue, Jan 22, 2013 at 3:55 AM, Amila Suriarachchi <[email protected]>wrote: >>>> >>>>> >>>>> >>>>> On Tue, Jan 22, 2013 at 5:16 PM, Pradeep Fernando <[email protected]>wrote: >>>>> >>>>>> Hi Anjana, >>>>>> >>>>>> I went through the ndatasource code. There we get >>>>>> ConfigurationContextSerice/ServerConfiguration/etc. While searching for >>>>>> their usages found out that we use those references to get clustering >>>>>> agents/registering AxisContextObservers/etc. >>>>>> >>>>>> How hard it is to decouple ndatasource implementation from other >>>>>> kernel dependencies. (we can depend on caching and logging of course) >>>>>> >>>>>> Theoretically what this component does is, populate a datasource and >>>>>> registering it against a JNDI lookup name. So we should be able to make >>>>>> this component kernel independent. >>>>>> >>>>> >>>>> This is the first part of making a minimal carbon kernel. We need to >>>>> get rid of Axis2 dependencies for all carbon kernel components. Is it >>>>> possible to implement this feature using some caching implementation like >>>>> Hazlecast? >>>>> >>>>> thanks, >>>>> Amila. >>>>> >>>>> >>>>>> >>>>>> your input is highly appreciated. >>>>>> >>>>>> thanks, >>>>>> --Pradeep >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Amila Suriarachchi* >>>>> >>>>> Software Architect >>>>> WSO2 Inc. ; http://wso2.com >>>>> lean . enterprise . middleware >>>>> >>>>> phone : +94 71 3082805 >>>>> >>>> >>>> >>>> >>>> -- >>>> *Anjana Fernando* >>>> Associate Technical Lead >>>> >>>> WSO2 Inc. | http://wso2.com >>>> lean . enterprise . middleware >>>> >>> >>> >>> >>> -- >>> *Amila Suriarachchi* >>> >>> Software Architect >>> WSO2 Inc. ; http://wso2.com >>> lean . enterprise . middleware >>> >>> phone : +94 71 3082805 >>> >> >> >> >> -- >> *Anjana Fernando* >> Associate Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > > > > -- > *Amila Suriarachchi* > > Software Architect > WSO2 Inc. ; http://wso2.com > lean . enterprise . middleware > > phone : +94 71 3082805 > -- *Anjana Fernando* Associate Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
