Well hazelcast has 3 issues: - like ignite it is big - it didnt impl cdi support last time i checked - it is not an apache project
that is why I ignored it (otherwise we would also consider infinispan and ehcache) 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-06-05 15:33 GMT-07:00 Andy Gumbrecht <agumbre...@tomitribe.com>: > I'm sure we leverage with hazelcast, so we should just ask. That would be > cool. > > Andy. > > http://www.tomitribe.com - @AndyGeeDe - On a small screen device. > On 5 Jun 2015 19:38, "jieryn" <jie...@gmail.com> wrote: > > > Can you elaborate about your use of jcache/jcs? Thanks! > > > > On Fri, Jun 5, 2015 at 12:42 PM, hwaastad <he...@waastad.org> wrote: > > > Not sure if I have too much saying in this matter but jcache/jcs is a > > very > > > nice "nice to have". > > > > > > Not 100% sure about payara, but wildfly does have a cache engine > > > incorporated. > > > > > > I use jcs/jcache in all my web projects and have nothing to complain > > about > > > :-) > > > > > > Br hw > > > > > > > > > > > > -- > > > View this message in context: > > > http://tomee-openejb.979440.n4.nabble.com/jcs-and-tomee-tp4675167p4675170.html > > > Sent from the TomEE Dev mailing list archive at Nabble.com. > > >
