2015-06-08 10:19 GMT+02:00 Jonathan Gallimore <[email protected]>:
> Hazelcast don't provide a CDI implementation at the moment - according to > this (sorry, cache link, the real page seems to have a DNS error at the > minute): > > http://webcache.googleusercontent.com/search?q=cache:M4As-MGA4GoJ:gregluck.com/blog/archives/category/jcache/+&cd=1&hl=en&ct=clnk&gl=uk > the CDI implementation for JCache should be provided by the CDI container - > i.e. us. > > I have had this working on TomEE using the reference implementation for the > CDI integration. I haven't tried the JCS CDI implementation, but I imagine > it works ok and would be portable to support other JCache providers. > > In terms of the original question, I'm definitely +1 on JCache being > available in TomEE, and I'm not too fussed what the default implementation > is. Benefits of JCS would be its size and the fact that its an Apache > project. That said, I'm aware we've done some work in the past to use > Hazelcast for stateful clustering so I could see benefits of using > Hazelcast to provide that and JCache support. > > Whichever route we go down, I think that swapping the cache provider should > be no more difficult that switching a .jar. > > s/swapping/putting it in your webapp/ just pushed it > Jon > > On Fri, Jun 5, 2015 at 11:41 PM, Andy Gumbrecht <[email protected]> > wrote: > > > Pretty sure they have cdi now. Need to check. Jon is up to date. > > > > http://www.tomitribe.com - @AndyGeeDe - On a small screen device. > > On 6 Jun 2015 00:36, "Romain Manni-Bucau" <[email protected]> wrote: > > > > > PS: just realized we have ehcache for cxf right? so can be a candidate > > > finally, wdyt? > > > > > > > > > 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:35 GMT-07:00 Romain Manni-Bucau <[email protected]>: > > > > > > > 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 <[email protected] > >: > > > > > > > >> 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" <[email protected]> wrote: > > > >> > > > >> > Can you elaborate about your use of jcache/jcs? Thanks! > > > >> > > > > >> > On Fri, Jun 5, 2015 at 12:42 PM, hwaastad <[email protected]> > > 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. > > > >> > > > > >> > > > > > > > > > > > > > > > > > -- > Jonathan Gallimore > http://twitter.com/jongallimore > http://www.tomitribe.com >
