Technically components like camel-jms/camel-sjms, camel-jdbc/camel-sql,
camel-jpa, camel-jcr, etc., all code to JSRs instead of particular
implementations. I don't think I've seen an equivalent for camel-camel ;)

Using the JSRs for a generic cache component would be nice because EHCache
and Infinispan both already support the JCache API, and Hazelcast is
working on adding support for it. That would make a better candidate for
the component named "camel-cache" as you could still even use EHCache with
it!


On 9 July 2014 09:47, ugol <ugo.land...@gmail.com> wrote:

> Do we have any example of a generic camel component with different
> implementations?
> Or should be camel-cache just a set of common API?
>
> On Wed, Jul 9, 2014 at 4:08 PM, ugol <ugo.land...@gmail.com> wrote:
> >> I like the idea of having some common api for caching in Camel. And
> >> making sure that this is the easiest and a good way to use caching.
> >>
> >> Altough there is also the jcache spec that Matt talks about. Not sure
> >> where that spec fits into this picture?
> >
> > In my idea, it's just that JSR107 and JSR 347 already cover what
> > caches/grids have in common, so we can use those JSR as an inspiration
> > for a good design.
> >
> >> Okay back to the cache. Sure guys we love contributions and surely I
> >> would like to see this moving forward.
> >
> > I'll see what I can do next weeks
> >
> > --
> > uL
> >
> > Pragmatist
> > http://blog.ugolandini.com
> > http://www.flickr.com/photos/ugol/
>
>
>
> --
> uL
>
> Pragmatist
> http://blog.ugolandini.com
> http://www.flickr.com/photos/ugol/
>



-- 
Matt Sicker <boa...@gmail.com>

Reply via email to