tag:blogger.com,1999:blog-106449775438946661.post4983458794898341076..comments2024-03-19T05:14:38.879-07:00Comments on Overcoming Fear: Evicting the Hibernate Domain Cache With SpringTim Myerhttp://www.blogger.com/profile/01514263555690798238noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-106449775438946661.post-18826845489598549982009-06-01T15:36:00.862-07:002009-06-01T15:36:00.862-07:00Hi Matt,
I appreciate the feedback and the questio...Hi Matt,<br />I appreciate the feedback and the question.<br />You make a good point that ehcache configuration is quite flexible, and, yes, the quartz 1.6.1 jar is almost twice the size of the ehcache 1.5.0 jar, but the quartz jar is still under 500K, which, while not ideal, is not so bad.<br />For this example, the use of Ehcache as the Hibernate cache implementation is not the primary focus. This use of a scheduled task to evict the cache can presumably be ported to other cache providers without the need to reconfigure them (if the other cache implementation supports cron-type scheduling for cache eviction at all).<br />That brings me to the requirement the use of quartz fulfills -- cache eviction at a definite time (say 01:15 every morning) rather than at an interval since the last time the application started. For that requirement, I could not find an Ehcache-specific setting and would be interested in seeing one if you could point me to the specific location in the configuration reference.<br />If I have misunderstood your point, or if you have another strategy for reaching the same end, I would be very interested in hearing about it.<br />Thanks again.<br />---Tim---Tim Myerhttps://www.blogger.com/profile/01514263555690798238noreply@blogger.comtag:blogger.com,1999:blog-106449775438946661.post-13760120448020315042009-06-01T09:03:31.093-07:002009-06-01T09:03:31.093-07:00I don't understand why you would use Quartz to sch...I don't understand why you would use Quartz to schedule class cache evictions when you can simply change the EHCACHE configuration which is already quite flexible (and doesn't require the relatively huge Quartz JARs).Matt Brockhttps://www.blogger.com/profile/11243952819216710867noreply@blogger.comtag:blogger.com,1999:blog-106449775438946661.post-90202165833373956262009-05-26T15:50:52.040-07:002009-05-26T15:50:52.040-07:00You might need to define bean for handlerMapping :...You might need to define bean for handlerMapping :<br />ControllerClassNameHandlerMapping<br />in the -servlet.xml.Anoshhttps://www.blogger.com/profile/06773476696564597460noreply@blogger.comtag:blogger.com,1999:blog-106449775438946661.post-66601132532341189812009-05-26T15:39:01.119-07:002009-05-26T15:39:01.119-07:00For Controllers request mappings, I think you can ...For Controllers request mappings, I think you can use convention over configuraion. Call the controller BookController and don't specify the uri mapping on the requestMapping annotation. Now the controller method show will have the uri - book/show. Method named all will me mapped to the uri book/all. To be honest I have not tried it.Anoshhttps://www.blogger.com/profile/06773476696564597460noreply@blogger.com