We allow defining data sources @ two levels targeting two different audiences.
Type1: Data sources defined in master-datasources.xml are used for server's internal storage requirements. This includes data source definitions like Registry database, User Store, etc. These data sources are modified by developers working on components for Carbon Servers. Type2: Then we also have data source defining capabilities for developers who will be using Carbon platform to write applications. This capabilities are exposed by WSO2 RSS (Relational Storage Server) & WSO2 AF. These data sources are dynamically loaded. So I feel it's acceptable for Type1 not to be loaded dynamically & Type2 to be loaded dynamically. On Thu, Feb 20, 2014 at 4:20 PM, Manoj Fernando <[email protected]> wrote: > Was wondering if it makes sense to dynamically load ALL datasources > defined in master-datasources.xml during bootstrap (well... we could > perhaps build an enable/disable switch on the config). > > Will be a useful feature when we may want to segregate various elements > that need to be persisted at different stores. > > Thoughts? > > Manoj > > -- > Manoj Fernando > Director - Solutions Architecture > > Contact: > LK - +94 112 145345 > Mob: +94 773 759340 > www.wso2.com > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- /sumedha b : bit.ly/sumedha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
