OK, so maybe the best thing for me is to create a simple main class, fire up the server and then run my app. Not a huge deal, but at least with ehcache 2.x you were able to to do it all through configuration.
On Mon, Nov 30, 2015 at 2:39 PM, Romain Manni-Bucau <[email protected]> wrote: > Starting the server? It is outside EE (even outside the EE server JVM) so I > guess not at the moment. > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> > > 2015-11-30 20:22 GMT+01:00 sgjava <[email protected]>: > > > OK, I see where you are boot strapping the server, but is there a way to > do > > it through all configuration? In other words, if I use: > > > > <dependency> > > <groupId>org.apache.commons</groupId> > > <artifactId>commons-jcs-jcache</artifactId> > > <version>2.0-SNAPSHOT</version> > > </dependency> > > > > This way it is agnostic across caching providers. I'm steering away from > > coding any JCache replication related code. > > > > > > > > -- > > View this message in context: > > > http://tomee-openejb.979440.n4.nabble.com/JCS-JCache-replication-tp4677031p4677033.html > > Sent from the TomEE Users mailing list archive at Nabble.com. > > > -- Steven P. Goldsmith
