Well, I definitely don't want our users to have to write code in order to configure cache-store in the Ignite configuration. I think providing factories out-of-the-box, even if they take 1 line of code to implement, may be the only solution here. We can add a sub-package called "stores" under "configuration" package.
Let's make sure that Sergey V. reviews it, given his expertise in this field. D. On Tue, Mar 24, 2015 at 9:10 AM, Alexey Kuznetsov <[email protected]> wrote: > Hi! > > Today discussed with Dmitriy we found that it will be great feature > if Schema Import utility will also generate bean for store factory in > Spring XML configuration. > > I faced following problem: because of dynamic caches CacheConfiguration > should be serializable, > but CacheJdbcPojoStore contains Datasource (not serializable in general). > > After internal discussion with Andrey Novikov and Yakov we came to decision > that we > could generate a factory class for datasouce for most popular RDBMS > (usually RDBMS supplied with vendor Datasource implementation) > > And if user will use something different or will need to use some other > Datasource > (c3po for example), he always could replace generated code with its own. > > Thoughts? > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com >
