[ 
https://issues.apache.org/jira/browse/CAMEL-8736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134062#comment-15134062
 ] 

ASF GitHub Bot commented on CAMEL-8736:
---------------------------------------

GitHub user lburgazzoli opened a pull request:

    https://github.com/apache/camel/pull/827

    CAMEL-8736 - Create new JCache component

    This PR is aimed to get some feedback on a new JCache component. 
    At the moment the component lacks a proper set of tests, documentation and 
some more functionalities I will add in the coming days.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/lburgazzoli/apache-camel CAMEL-8736

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/827.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #827
    
----
commit d691db6bf7d5bf674c65eb0594cf9c376472f701
Author: lburgazzoli <[email protected]>
Date:   2016-02-05T12:04:44Z

    CAMEL-8736 - Create new JCache component

----


> Create new component using Hazelcast JCache implementation
> ----------------------------------------------------------
>
>                 Key: CAMEL-8736
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8736
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Andrea Cosentino
>            Priority: Minor
>              Labels: caching
>             Fix For: Future
>
>
> Starting from version 3.3.1, Hazelcast has its own implementation of JCache. 
> I think it can be useful to include it in Camel as a component.
> Edit:
> Looking at the implementation it looks like this new feature is outside the 
> HazelcastInstance. So this improvement can be part of a new component, like 
> camel-hazelcast-cache, but it can't be inside camel-hazelcast component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to