[
https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Klimczak updated CAMEL-3867:
----------------------------------
Attachment: camel-cache.cleanupAndLitenersRef.patch
Final version as got jms replication working with osgi test.
Please note that this patch do not contains any jms replication functionality.
It is just prepared to let you do it using spring ref functionality.
Sorry for uploading same fail many times. Working at nights is not a good idea
for longer period of time.
Please let me know if you have any questions.
> 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
> Priority: Minor
> Labels: camel-cache, ehcache, improvement, listener, replication
> Fix For: 2.8.0
>
> Attachments: camel-cache.cleanupAndLitenersRef.patch,
> camel-itest-osgi.CacheManagerFactoryRefTest.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
