History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CACHE-99
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Lars Torunski
Reporter: Davide Baroncelli
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
OSCache

Use lazy initialization in cache filter in order to ease spring integration

Created: 19/Aug/04 08:50 AM   Updated: 01/May/07 11:01 AM
Component/s: Filters
Affects Version/s: 2.0.2
Fix Version/s: 2.4

Issue Links:
Related
This issue relates to:
CACHE-215 Setting CacheFilter parameters runtime Critical Closed
 


 Description  « Hide
I want to use oscache filter in a spring controlled (and configured) environment: since all of my system is configured in spring files I have implemented a factory bean allowing me to initialize oscache with a spring bean. The only problem is that if I use filters, they are initialized before I have a chance to initialize spring (in websphere 5.1), and since they do initialize eagerly the cache by loading properties from the classpath, things get messed up. I fixed it by creating a clone of CacheFilter that initializes lazily the admin object in the doFilter instead of doing it in the init method: it would be good if this could be added as a configuration option.

 All   Comments   Change History      Sort Order:
Andres March - [22/Sep/04 11:22 AM ]
Submit a patch and I will review it.

Lars Torunski - [26/Feb/07 02:19 PM ]
Do you want to set all upcoming CacheFilter configuration parameter?

time
scope
cron
fragment
nocache
lastModified
max-age
expires
ICacheKeyProvider
ICacheGroupsProvider
EntryRefreshPolicy
oscache-properties-file

Lars Torunski - [04/Mar/07 12:10 PM ]
getter/setter for 'oscache-properties-file' is still open.
TO DO: Document spring integration.