You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2015/06/05 17:02:48 UTC
jcs and tomee
Hi guys
didnt get much feedback about this one so let's try another time.
The question is: what do we do for JCache. Strictly speaking it is not in
the spec but do we add it in plus distrib?
If yes there is another question: do we use JCS or Ignite?
personally I am almost tempted to remove it but having it has some
advantages as well
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>
Re: jcs and tomee
Posted by Jonathan Gallimore <jg...@tomitribe.com>.
Very nice! I'll give that a go.
Jon
On Mon, Jun 8, 2015 at 3:05 PM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> 2015-06-08 10:19 GMT+02:00 Jonathan Gallimore <jg...@tomitribe.com>:
>
> > 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 <
> agumbrecht@tomitribe.com>
> > 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" <rm...@gmail.com>
> 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 <rmannibucau@gmail.com
> >:
> > > >
> > > > > 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 <
> agumbrecht@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" <ji...@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.
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Jonathan Gallimore
> > http://twitter.com/jongallimore
> > http://www.tomitribe.com
> >
>
--
Jonathan Gallimore
http://twitter.com/jongallimore
http://www.tomitribe.com
Re: jcs and tomee
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2015-06-08 10:19 GMT+02:00 Jonathan Gallimore <jg...@tomitribe.com>:
> 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 <ag...@tomitribe.com>
> 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" <rm...@gmail.com> 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 <rm...@gmail.com>:
> > >
> > > > 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 <agumbrecht@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" <ji...@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.
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
>
>
> --
> Jonathan Gallimore
> http://twitter.com/jongallimore
> http://www.tomitribe.com
>
Re: jcs and tomee
Posted by Jonathan Gallimore <jg...@tomitribe.com>.
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.
Jon
On Fri, Jun 5, 2015 at 11:41 PM, Andy Gumbrecht <ag...@tomitribe.com>
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" <rm...@gmail.com> 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 <rm...@gmail.com>:
> >
> > > 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 <ag...@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" <ji...@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.
> > >> >
> > >>
> > >
> > >
> >
>
--
Jonathan Gallimore
http://twitter.com/jongallimore
http://www.tomitribe.com
Re: jcs and tomee
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
Really good promo if that works out.
http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
On 6 Jun 2015 00:41, "Andy Gumbrecht" <ag...@tomitribe.com> 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" <rm...@gmail.com> 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 <rm...@gmail.com>:
>>
>> > 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 <ag...@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" <ji...@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.
>> >> >
>> >>
>> >
>> >
>>
>
Re: jcs and tomee
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
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" <rm...@gmail.com> 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 <rm...@gmail.com>:
>
> > 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 <ag...@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" <ji...@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.
> >> >
> >>
> >
> >
>
Re: jcs and tomee
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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 <rm...@gmail.com>:
> 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 <ag...@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" <ji...@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.
>> >
>>
>
>
Re: jcs and tomee
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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 <ag...@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" <ji...@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.
> >
>
Re: jcs and tomee
Posted by Andy Gumbrecht <ag...@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" <ji...@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.
>
Re: jcs and tomee
Posted by Mark Struberg <st...@yahoo.de>.
> Means we can use jaxrs 1.1 in tomee 1.7 br1nch for instance?
Yes this seems exactly what Oracle and IBM seem to do. And Oracle does it even for ‚final‘ releases. I have no clue how they manage to pass the signature tests though. Probably we are fine with just have backward compat signatures.
LieGrue,
strub
> Am 08.06.2015 um 09:27 schrieb Romain Manni-Bucau <rm...@gmail.com>:
>
> Le 8 juin 2015 00:18, "Mark Struberg" <st...@yahoo.de> a écrit :
>>
>> Yes, and as confirmed by Reza Rahman yesterday it is perfectly allowed to
> have other spec impls in our distro.
>> This seems to even include LATER versions of a spec which is contained in
> an EE version - at least if it is backward compatible. Reza explained that
> both IBM (with Liberty profile) and Oracle itself (With 12.1.2) are EE6
> containers which ship with many EE7 APIs and projects in there. So as
> Oracle and IBM are doing this and we got the OK from an Oracle evangelist
> it seems to really be perfectly legit.
>>
>
> Means we can use jaxrs 1.1 in tomee 1.7 br1nch for instance?
>
>> This allows for a MUCH more eager update of TomEE features in the future!
>> So let’s just add JCS as JCache impl (smallesst one) and add docs how
> people can easily replace this with other impls.
>>
>
> It is there foe month just the code to ignore it needs to be done. Ill
> check in few days. Should one line in IRLClassLoaderFirst
>
>> LieGrue,
>> strub
>>
>>
>>> Am 07.06.2015 um 13:27 schrieb hwaastad <he...@waastad.org>:
>>>
>>> Sorry,
>>> you are right.
>>>
>>> Just want to comment that the reason is that cache (nodes) has the
> ability
>>> to to be reset/updated from a remote node, not being member of the
> storage
>>> cluster.
>>>
>>> Anyways, since jsr-107 is a part of ee8 (?) and the plus distribution
> still
>>> is "outside" certification, I see no reason for not adding cache to the
>>> features.
>>>
>>> my 2 cents, anyways :-)
>>>
>>> br hw
>>>
>>>
>>>
>>> --
>>> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/jcs-and-tomee-tp4675167p4675188.html
>>> Sent from the TomEE Dev mailing list archive at Nabble.com.
>>
Re: jcs and tomee
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Le 8 juin 2015 00:18, "Mark Struberg" <st...@yahoo.de> a écrit :
>
> Yes, and as confirmed by Reza Rahman yesterday it is perfectly allowed to
have other spec impls in our distro.
> This seems to even include LATER versions of a spec which is contained in
an EE version - at least if it is backward compatible. Reza explained that
both IBM (with Liberty profile) and Oracle itself (With 12.1.2) are EE6
containers which ship with many EE7 APIs and projects in there. So as
Oracle and IBM are doing this and we got the OK from an Oracle evangelist
it seems to really be perfectly legit.
>
Means we can use jaxrs 1.1 in tomee 1.7 br1nch for instance?
> This allows for a MUCH more eager update of TomEE features in the future!
> So let’s just add JCS as JCache impl (smallesst one) and add docs how
people can easily replace this with other impls.
>
It is there foe month just the code to ignore it needs to be done. Ill
check in few days. Should one line in IRLClassLoaderFirst
> LieGrue,
> strub
>
>
> > Am 07.06.2015 um 13:27 schrieb hwaastad <he...@waastad.org>:
> >
> > Sorry,
> > you are right.
> >
> > Just want to comment that the reason is that cache (nodes) has the
ability
> > to to be reset/updated from a remote node, not being member of the
storage
> > cluster.
> >
> > Anyways, since jsr-107 is a part of ee8 (?) and the plus distribution
still
> > is "outside" certification, I see no reason for not adding cache to the
> > features.
> >
> > my 2 cents, anyways :-)
> >
> > br hw
> >
> >
> >
> > --
> > View this message in context:
http://tomee-openejb.979440.n4.nabble.com/jcs-and-tomee-tp4675167p4675188.html
> > Sent from the TomEE Dev mailing list archive at Nabble.com.
>
Re: jcs and tomee
Posted by Mark Struberg <st...@yahoo.de>.
Yes, and as confirmed by Reza Rahman yesterday it is perfectly allowed to have other spec impls in our distro.
This seems to even include LATER versions of a spec which is contained in an EE version - at least if it is backward compatible. Reza explained that both IBM (with Liberty profile) and Oracle itself (With 12.1.2) are EE6 containers which ship with many EE7 APIs and projects in there. So as Oracle and IBM are doing this and we got the OK from an Oracle evangelist it seems to really be perfectly legit.
This allows for a MUCH more eager update of TomEE features in the future!
So let’s just add JCS as JCache impl (smallesst one) and add docs how people can easily replace this with other impls.
LieGrue,
strub
> Am 07.06.2015 um 13:27 schrieb hwaastad <he...@waastad.org>:
>
> Sorry,
> you are right.
>
> Just want to comment that the reason is that cache (nodes) has the ability
> to to be reset/updated from a remote node, not being member of the storage
> cluster.
>
> Anyways, since jsr-107 is a part of ee8 (?) and the plus distribution still
> is "outside" certification, I see no reason for not adding cache to the
> features.
>
> my 2 cents, anyways :-)
>
> br hw
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/jcs-and-tomee-tp4675167p4675188.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: jcs and tomee
Posted by hwaastad <he...@waastad.org>.
Sorry,
you are right.
Just want to comment that the reason is that cache (nodes) has the ability
to to be reset/updated from a remote node, not being member of the storage
cluster.
Anyways, since jsr-107 is a part of ee8 (?) and the plus distribution still
is "outside" certification, I see no reason for not adding cache to the
features.
my 2 cents, anyways :-)
br hw
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/jcs-and-tomee-tp4675167p4675188.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: jcs and tomee
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2015-06-06 8:55 GMT+02:00 hwaastad <he...@waastad.org>:
> Hi,
> an example would be that we have a cluster of web servers providing
> mulitlanguage dynamic forms (based on primefaces ext dynaforms) to both jsf
> clients and javascript clients. The cost of building forms in terms of
> time,
> is quite big so the only way of making it smooth is by using a multicast
> (jcs) cache.
> Several ways of managing the cache, but we ended up using a jms queue for
> forced cache updates.
>
surely not the right list but wonder why jms? jcs supports the distribution
>
> br hw
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/jcs-and-tomee-tp4675167p4675177.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>
Re: jcs and tomee
Posted by hwaastad <he...@waastad.org>.
Hi,
an example would be that we have a cluster of web servers providing
mulitlanguage dynamic forms (based on primefaces ext dynaforms) to both jsf
clients and javascript clients. The cost of building forms in terms of time,
is quite big so the only way of making it smooth is by using a multicast
(jcs) cache.
Several ways of managing the cache, but we ended up using a jms queue for
forced cache updates.
br hw
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/jcs-and-tomee-tp4675167p4675177.html
Sent from the TomEE Dev mailing list archive at Nabble.com.
Re: jcs and tomee
Posted by jieryn <ji...@gmail.com>.
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.
Re: jcs and tomee
Posted by hwaastad <he...@waastad.org>.
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.
Re: jcs and tomee
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Just few notes for people not having checked:
- ignote = 6M
- jcs = 700K
keeping it means we need to filter provider to support overrides (not a big
deal we already do for other stuff)
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 9:40 GMT-07:00 Mark Struberg <st...@yahoo.de>:
> +1 for keeping it and using jcs.
>
> LieGrue,
> strub
>
> > Am 05.06.2015 um 17:02 schrieb Romain Manni-Bucau <rmannibucau@gmail.com
> >:
> >
> > Hi guys
> >
> > didnt get much feedback about this one so let's try another time.
> >
> > The question is: what do we do for JCache. Strictly speaking it is not in
> > the spec but do we add it in plus distrib?
> >
> > If yes there is another question: do we use JCS or Ignite?
> >
> > personally I am almost tempted to remove it but having it has some
> > advantages as well
> >
> > 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>
>
>
Re: jcs and tomee
Posted by Mark Struberg <st...@yahoo.de>.
+1 for keeping it and using jcs.
LieGrue,
strub
> Am 05.06.2015 um 17:02 schrieb Romain Manni-Bucau <rm...@gmail.com>:
>
> Hi guys
>
> didnt get much feedback about this one so let's try another time.
>
> The question is: what do we do for JCache. Strictly speaking it is not in
> the spec but do we add it in plus distrib?
>
> If yes there is another question: do we use JCS or Ignite?
>
> personally I am almost tempted to remove it but having it has some
> advantages as well
>
> 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>