Printable View
as the springmodules projects seems pretty dead, and its cache module doesn't work in spring 3.0, i'm having a look at either write my own aop stuff for caching, or use the ehcache-spring-annotations fork.
does anyone have experience with using the fork in a production / live environment? i mean is it mature enough?
thanks
cross linking to a similar question here
Quote:
Originally Posted by aVoice
I'm looking to use this, but have no idea how to configure the timeouts for those cachegroups. I can't see any examples on their site.
To answer my post - you need to define these in your ehcache.xml. check the ehcache.org for details.
I have this setup for some of my DAOs and it seems to work.
If you are trying to use Spring 3.0, there is a new project listed at the end of this thread that uses annotations for caching. I haven't had time to try it out yet, but it might be worth looking into.
http://forum.springsource.org/showth...t=47953&page=2
I should have said, I am using ehcache-spring-annotations now and seems to work. My previous posts were in relation to this new project.
As one of the authors of ehcache-spring-annotations I'd like to assure you that it is very much production ready. Nick (the other author) and I wrote it out of a need in several high-traffic applications we work on and we haven't had any issues with it.
While I haven't actually done performance benchmarks on this versus spring-modules-cache I would surmise that it is significantly faster due to improvements in key generation and a significant reduction in the code that is executed by the caching aspect.
Is there a similar project that supports JBoss Cache or if not how difficult is it to adapt ehcache-spring-annotation to work with JBoss?
There isn't a similar project that I know of.
We implemented ehcache-spring-annotations for ehcache specifically so there is no abstract away from the Ehcache classes. It likely could be done but I'm not sure how much work it would be.
I am going to try and modify your framework to make it JBoss-compatible. Although, I have never modified and static-linked an opensource project before. What are the rules with regards to the licensing and copyright/left? am I allowed to change the packaging or inject my code to the project using the same package names?
The new project (if successful) will be used internally in a proprietary enterprise application. Although I will be more than happy to contribute it back to the mother project to be assessed and possibly added to the framework if deemed good enough and upon permission from my company.
Thanks.