You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Piotr Klimczak (JIRA)" <ji...@apache.org> on 2011/04/14 23:56:05 UTC
[jira] [Created] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
camel-cache- improve ehcache configuration by reference RegisteredEventListeners
--------------------------------------------------------------------------------
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
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 (via spring/blueprint ref.) during endpoint construction.
This will ease configuration of listeners 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 for all cache endpoints!
SO SIMPLY! :)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025651#comment-13025651 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
Sure! No problem. Will do that this afternoon.
I'm very happy to see some activity here :)
BTW. I did not received an email with your comment :/ Found Ben O'Day changes accidentally. So i guess it is better idea to periodically review unresolved issues than waiting for email notification.
> 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029306#comment-13029306 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
Now i can say i am very happy :)
Thank you guys!
One more thing. I am going to edit camel-cache docs, i have already sent ICLA to apache and send an information to camel dev forum. What else do i have to do to be able to edit great apache docs? :)
Thanks in advance!
> 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
[jira] [Issue Comment Edited] (CAMEL-3867) camel-cache- improve
ehcache configuration by reference RegisteredEventListeners and
CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025651#comment-13025651 ]
Piotr Klimczak edited comment on CAMEL-3867 at 4/27/11 7:20 AM:
----------------------------------------------------------------
No at all! No problem. Will do that this afternoon.
I'm very happy to see some activity here :)
BTW. I did not received an email with your comment :/ Found Ben O'Day changes accidentally. So i guess it is better idea to periodically review unresolved issues than waiting for email notification.
was (Author: nannou9):
Sure! No problem. Will do that this afternoon.
I'm very happy to see some activity here :)
BTW. I did not received an email with your comment :/ Found Ben O'Day changes accidentally. So i guess it is better idea to periodically review unresolved issues than waiting for email notification.
> 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020295#comment-13020295 ]
Claus Ibsen commented on CAMEL-3867:
------------------------------------
See here about improving docs
http://camel.apache.org/contributing.html
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
>
> 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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020058#comment-13020058 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
In my opinion it will be really useful. And of course I'll prepare the patch :)
For now configuring ehcache is very painful as there is no wildcards.
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
>
> 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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 for all cache endpoints!
> SO SIMPLY! :)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CAMEL-3867) camel-cache- improve
ehcache configuration by reference RegisteredEventListeners and
CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021238#comment-13021238 ]
Piotr Klimczak edited comment on CAMEL-3867 at 4/18/11 8:40 PM:
----------------------------------------------------------------
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 file many times. Working at nights is not a good idea for longer period of time.
Please let me know if you have any questions.
was (Author: nannou9):
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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ 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
reworked adding cacheLoaderRegistry.
Also fixed 1 possible patch conflict on eventListenereRegistry.
> 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
> Attachments: 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-3867.
---------------------------------
Resolution: Fixed
Applied patch with thanks to Piotr.
> 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Klimczak updated CAMEL-3867:
----------------------------------
Description:
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 (via spring/blueprint ref.) during endpoint construction.
This will ease configuration of listeners 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 for all cache endpoints!
SO SIMPLE! :)
was:
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 (via spring/blueprint ref.) during endpoint construction.
This will ease configuration of listeners 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 for all cache endpoints!
SO SIMPLY! :)
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
>
> 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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021264#comment-13021264 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
This patch is needed by: https://issues.apache.org/jira/browse/CAMEL-3880
To finalize all I will prepare changes in camel-cache component documentation soon.
The latest step will be a full tutorial.
Have a FUN! :)
> 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
[jira] [Issue Comment Edited] (CAMEL-3867) camel-cache- improve
ehcache configuration by reference RegisteredEventListeners
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020058#comment-13020058 ]
Piotr Klimczak edited comment on CAMEL-3867 at 4/14/11 10:00 PM:
-----------------------------------------------------------------
In my opinion it will be really useful. And of course I'll prepare the patch soon :)
For now configuring ehcache is very painful as there is no wildcards.
BTW. How can i change the docs or make a patch to Apache docs?
was (Author: nannou9):
In my opinion it will be really useful. And of course I'll prepare the patch :)
For now configuring ehcache is very painful as there is no wildcards.
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
>
> 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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020834#comment-13020834 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
BTW. It would be much easier for all if I could work on my own branch :)
> 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020832#comment-13020832 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
Summary
All files are diffs to current trunk, where
1. camel-cache.cleanupAndLitenersRef.patch- apply to https://svn.apache.org/repos/asf/camel/trunk/components/camel-cache
contains:
* added URI configuration option named: eventListenerRegistry which is a ref to CacheEventListenerRegistry type
* added URI configuration option named: cacheLoaderRegistry which is a ref to CacheLoaderRegistry type
* added unit test to test cache event listener/loader behaviour- to make sure that referenced listeners/loaders are invoked
* cleaned up consumer and producer by moving same code do the CacheEndpoint
* removed cache stop from consumer/producer and moved to the endpoint- as I understand the camel it will prevent removing cache when route is stopped manually.
* added unit test to test route manual shutdown and cache being still alive
2. camel-itest-osgi.CacheRouteManagementTest.patch- osgi test of manual managing routes (manual shutdown test using context.stopRoute).
3. camel-itest-osgi.CacheManagerFactoryRefTest.patch- simple osgi test of referencing CacheManagerFactory and configuring ehcache using xml file.
The 2. and 3. both are optional and if you want to apply them to: https://svn.apache.org/repos/asf/camel/trunk/tests/camel-itest-osgi
both adds osgi unit test
That's it.
But there is still one thing that puzzles me, it is:
* added URI configuration option named: cacheLoaderRegistry which is a ref to CacheLoaderRegistry type
During writing an osgi test for jms replication i have found that the cacheLoaderRegistry will be more usable with some more improvements.
So we have 2 options now:
a) we will wait until i will write fully working jms replication osgi unit test (using cacheLoaders and cacheEventListeners)
b) you can apply the patch to trun and then will wait for another patch.
Decision is your. Just teake a look at the code.
> 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Klimczak updated CAMEL-3867:
----------------------------------
Attachment: (was: camel-cache.cleanupAndLitenersRef.txt)
> 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
> Attachments: 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Klimczak updated CAMEL-3867:
----------------------------------
Attachment: camel-itest-osgi.CacheRouteManagementTest.patch
camel-itest-osgi.CacheManagerFactoryRefTest.patch
camel-cache.cleanupAndLitenersRef.patch
Re-created patches with latest changes.
Have a FUN! :)
> 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-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
[jira] [Issue Comment Edited] (CAMEL-3867) camel-cache- improve
ehcache configuration by reference RegisteredEventListeners and
CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020834#comment-13020834 ]
Piotr Klimczak edited comment on CAMEL-3867 at 4/17/11 5:54 PM:
----------------------------------------------------------------
If my summary is not sufficient, please do not hesitate to ask me about anything...
BTW. It would be much easier for all if I could work on my own branch :)
was (Author: nannou9):
BTW. It would be much easier for all if I could work on my own branch :)
> 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020767#comment-13020767 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
CacheLoaders are also needed. The patch needs small reworking.
> 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
> Attachments: camel-cache.cleanupAndLitenersRef.txt, 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Klimczak updated CAMEL-3867:
----------------------------------
Attachment: (was: camel-cache.cleanupAndLitenersRef.patch)
> 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
> Attachments: 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020757#comment-13020757 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
This patch is a continuation of bringing camel-cache to clustered world. I guess 75% is already done. Those 25% is:
- making a patch to smx ehcache bundle (done but patch not prepared yet, will upload the patch in parallel with below osgi unit test)
- provide osgi unit test to test jms replication (not started yet)
Then I will prepare a working example for tutorial purpose and of course a full tutorial telling about how to use ehcache and replication in real life :)
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
> Attachments: camel-cache.cleanupAndLitenersRef.txt, 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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020749#comment-13020749 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
I've made a little more changes- I've done some code cleanup.
I do understand that code cleanups are dificult to analize but it is still better option than improving bad code.
Here is the list what I've done in this patch:
- added URI configuration option named: eventListenerRegistry which is a ref to CacheEventListenerRegistry type
- added unit test to test event listener behaviour- to make sure that referenced listeners are invoked (CacheEventListenerRegistryTest)
- cleaned up consumer and producer by moving same code do the CacheEndpoint
- removed cache stop from consumer/producer and moved to the endpoint- as I understand the camel it will prevent removing cache when route is stopped manually.
- added unit test to test route manual shutdown and cache being still alive
If you don't like those changes, then please give me a sign.
Plese note that i did not want to divide it to 2 improvements as it'll be quite complicated.
Plese also note that applying this patch to trunk will casuse the my last osgi unit test to stop working, as the cache manager factory will not be initialized until first routing will be done.
Will attach a patch soon.
Should I make new issue for that? or simply attach a patch to itest here?
Hope you like it :)
HAVE A FUN!
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
> Attachments: camel-cache.cleanupAndLitenersRef.txt
>
>
> 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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023168#comment-13023168 ]
Claus Ibsen commented on CAMEL-3867:
------------------------------------
There has been some changes on trunk in camel-cache in terms of cache keys.
Do you mind re-creating patches from trunk?
> 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
[jira] [Issue Comment Edited] (CAMEL-3867) camel-cache- improve
ehcache configuration by reference RegisteredEventListeners and
CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025651#comment-13025651 ]
Piotr Klimczak edited comment on CAMEL-3867 at 5/4/11 6:56 PM:
---------------------------------------------------------------
No problem. Will do that this afternoon.
I'm very happy to see some activity here :)
BTW. I did not received an email with your comment :/ Found Ben O'Day changes accidentally. So i guess it is better idea to periodically review unresolved issues than waiting for email notification.
was (Author: nannou9):
No at all! No problem. Will do that this afternoon.
I'm very happy to see some activity here :)
BTW. I did not received an email with your comment :/ Found Ben O'Day changes accidentally. So i guess it is better idea to periodically review unresolved issues than waiting for email notification.
> 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-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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029318#comment-13029318 ]
Claus Ibsen commented on CAMEL-3867:
------------------------------------
Piotr can you point out your name on the Apache CLA site?
http://people.apache.org/committer-index.html#unlistedclas
> 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ 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.txt
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
> Attachments: camel-cache.cleanupAndLitenersRef.txt
>
>
> 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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Klimczak updated CAMEL-3867:
----------------------------------
Description:
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! :)
was:
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 (via spring/blueprint ref.) during endpoint construction.
This will ease configuration of listeners 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 for all cache endpoints!
SO SIMPLE! :)
Summary: camel-cache- improve ehcache configuration by reference RegisteredEventListeners and CacheLoaders (was: camel-cache- improve ehcache configuration by reference RegisteredEventListeners)
> 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
> Attachments: camel-cache.cleanupAndLitenersRef.txt, 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-3867:
-------------------------------
Fix Version/s: 2.8.0
> 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020810#comment-13020810 ]
Claus Ibsen commented on CAMEL-3867:
------------------------------------
Piotr do you mind summarize which patches is needed to be applied (based on whats diff from the trunk). Just to be sure we do it right.
> 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Klimczak updated CAMEL-3867:
----------------------------------
Attachment: camel-itest-osgi.CacheRouteManagementTest.patch
An OSGi copy of camel-cache unit test that test manual shutdown cache route.
Apply it if you want'em more (i mean more osgi tests :))
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
> Attachments: camel-cache.cleanupAndLitenersRef.txt, 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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029313#comment-13029313 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
Thanks Claus for response! :)
My username on confluence is: nannou9
Same as in JIRA.
> 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029308#comment-13029308 ]
Piotr Klimczak commented on CAMEL-3867:
---------------------------------------
Please note that i already have a confluence account but when i click edit on the bottom of page I get: Not Permitted.
> 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
[jira] [Issue Comment Edited] (CAMEL-3867) camel-cache- improve
ehcache configuration by reference RegisteredEventListeners and
CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025664#comment-13025664 ]
Piotr Klimczak edited comment on CAMEL-3867 at 4/27/11 9:10 AM:
----------------------------------------------------------------
Recreated patches to let it work with latest trunk changes.
Have a FUN! :)
was (Author: nannou9):
Re-created patches with latest changes.
Have a FUN! :)
> 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-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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Klimczak updated CAMEL-3867:
----------------------------------
Attachment: camel-itest-osgi.CacheManagerFactoryRefTest.patch
Patch to osgi test cases due to start/stop logic change. Now test will do some route before any assertion
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
> Attachments: camel-cache.cleanupAndLitenersRef.txt, camel-itest-osgi.CacheManagerFactoryRefTest.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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020751#comment-13020751 ]
Claus Ibsen commented on CAMEL-3867:
------------------------------------
Keep 'em coming Piotr. Its fine to just attach a 2nd patch for the change in that other test.
I will review and apply this patch in a bit.
> camel-cache- improve ehcache configuration by reference RegisteredEventListeners
> --------------------------------------------------------------------------------
>
> 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
> Attachments: camel-cache.cleanupAndLitenersRef.txt
>
>
> 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 (via spring/blueprint ref.) during endpoint construction.
> This will ease configuration of listeners 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 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ 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
> 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
> 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
[jira] [Updated] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Piotr Klimczak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Klimczak updated CAMEL-3867:
----------------------------------
Attachment: (was: camel-cache.cleanupAndLitenersRef.patch)
> 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-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
[jira] [Commented] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029309#comment-13029309 ]
Claus Ibsen commented on CAMEL-3867:
------------------------------------
Whats your username on confluence? I can assign you karma so you can edit.
> 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
[jira] [Assigned] (CAMEL-3867) camel-cache- improve ehcache
configuration by reference RegisteredEventListeners and CacheLoaders
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-3867:
-----------------------------------
Assignee: Willem Jiang
> 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