And BTW, over the weekend I committed a new connection pool to Cayenne that is non-blocking and supports connection validation query. So barring any possible bugs in this new code, it should be on par with more "high-end" pools in performance and failover. So you might just build M3 from master and use the example as is.
Andrus > On May 4, 2015, at 9:40 AM, Andrus Adamchik <[email protected]> wrote: > > Our example on GitHub should work with built-in Cayenne connection pool: > > ServerRuntime runtime = new ServerRuntimeBuilder() > .addConfig("cayenne-project.xml") > .addModule(OsgiModuleBuilder > .forProject(Activator.class) > .withDriver(org.apache.derby.jdbc.Driver42.class) > .module()) > .build(); > > > I suspect it should also work with older DBCP 1 pool, if you could get this > into OSGi. But this hasn't been tested. > > Andrus > > >> On May 4, 2015, at 4:08 AM, mporru <[email protected]> wrote: >> >> Hi Andrus, >> sorry for my late reply. And thanks for your comments. >> >> Do you have any suggestion on how can I move forward in the short term? >> >> I mean, shall I try a different pooling technology (as you did, if I >> understood properly)? >> In that case, do you mind to point me to an example or write me few lines >> how to have Cayenne running with this other pooling library? >> >> Thank you again, >> Matteo >> >> >> >> -- >> View this message in context: >> http://cayenne.195.n3.nabble.com/Cayenne-4-0-M2-and-OSGi-classloading-issue-tp4026812p4026840.html >> Sent from the Cayenne - Dev mailing list archive at Nabble.com. >> > >
