camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Klimczak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache configuration by reference RegisteredEventListeners and CacheLoaders
Date Thu, 05 May 2011 13:33:03 GMT

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

Piotr Klimczak commented on CAMEL-3867:
---------------------------------------

Well, i am not listed there yet. Not sure why.
I have received a message from Sam Ruby that my ICLA was filed in ASF records and I should
advise the project PMC.

Do you have any idea why am i not listed yet?

> camel-cache- improve ehcache configuration by reference RegisteredEventListeners and
CacheLoaders
> -------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3867
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3867
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cache
>         Environment: Osgi/Spring based
>            Reporter: Piotr Klimczak
>            Assignee: Willem Jiang
>            Priority: Minor
>              Labels: camel-cache, ehcache, improvement, listener, replication
>             Fix For: 2.8.0
>
>         Attachments: camel-cache.cleanupAndLitenersRef.patch, camel-cache.cleanupAndLitenersRef.patch,
camel-itest-osgi.CacheManagerFactoryRefTest.patch, camel-itest-osgi.CacheManagerFactoryRefTest.patch,
camel-itest-osgi.CacheRouteManagementTest.patch, camel-itest-osgi.CacheRouteManagementTest.patch
>
>
> The thing is, that cache names can be a dynamic list. But ehcache is expecting to get
static list (known before start) on it's xml configuration file. Ehcache provides some defaults
config. for new caches with some exceptions. One of them are cache listeners (like replication
listeners).
> So the thing is, to give ability to define listeners and cache loaders (via spring/blueprint
ref.) during endpoint construction.
> This will ease configuration of listeners/loaders as xml static list of listeners (per
cache) will not be needed anymore. Instead of very long list which you have to keep up to
date, you could define one list of listeners/loaders for all cache endpoints!
> SO SIMPLE! :)

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

Mime
View raw message