Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 8 Apr 2011 21:58:05 +0000 (UTC)
From: "Piotr Klimczak (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1891672441.45245.1302299885778.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <171091327.43862.1302272045656.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CAMEL-3849) No possibility to enable ehcache
 clustering as: ehcache.xml is ignored and there is no possibility to set
 cacheManagerFactory described camel-cache docs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Klimczak updated CAMEL-3849:
----------------------------------

    Description: 
This bug is caused by more than one problem as:
1. camel-cache bundle provides ehcache.xml config which is ignored so then default ehcache-failsafe.xml is taken by ehcache bundle.
2. according to camel-cache docs there is a way to set cacheManagerFactory but it seems to be not implemented as
a) default CacheManagerFactory instance is created when when CacheComponent is instantiated.
b) setter method: public void setCacheManagerFactory(CacheManagerFactory cacheManagerFactory) is used just nowhere.
c) there is no suitable filed in class CacheConfiguration

All above problems cause camel-cache to be not able to work in java- clustered world as default failsafe config. is really failsafe- w/o clustering.


  was:
This bug seems to be more than one problem as:
1. camel-cache bundle provides ehcache.xml config which is ignored so then default ehcache-failsafe.xml is taken by ehcache bundle.
2. according to camel-cache docs there is a way to set cacheManagerFactory but it seems to be not implemented as
a) default CacheManagerFactory instance is created when when CacheComponent is instantiated.
b) setter method: public void setCacheManagerFactory(CacheManagerFactory cacheManagerFactory) is used just nowhere.
c) there is not suitable filed in class CacheConfiguration

All above problems cause camel-cache to be not able to work in java- clustered world as default failsafe config. is really failsafe- w/o clustering.


> No possibility to enable ehcache clustering as: ehcache.xml is ignored and there is no possibility to set cacheManagerFactory described camel-cache docs
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3849
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3849
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cache
>    Affects Versions: 2.6.0, 2.7.0
>         Environment: any
>            Reporter: Piotr Klimczak
>              Labels: cacheManagerFactory, camel-cache, cluster, clustering, osgi
>
> This bug is caused by more than one problem as:
> 1. camel-cache bundle provides ehcache.xml config which is ignored so then default ehcache-failsafe.xml is taken by ehcache bundle.
> 2. according to camel-cache docs there is a way to set cacheManagerFactory but it seems to be not implemented as
> a) default CacheManagerFactory instance is created when when CacheComponent is instantiated.
> b) setter method: public void setCacheManagerFactory(CacheManagerFactory cacheManagerFactory) is used just nowhere.
> c) there is no suitable filed in class CacheConfiguration
> All above problems cause camel-cache to be not able to work in java- clustered world as default failsafe config. is really failsafe- w/o clustering.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira