Hey Derek, > You're probably on the right track, although I want to clarify: are the > entity and its collections something that won't change often? Do you need > transactional views on it (i.e. changes made by one session are immediately > visible in others)? From your question about caching at Boot it sounds like > this may be something that never changes or very infrequently. If it's > something that never changes then you may be able to just load it in Boot, > touch the collections (to force the lazy retrieval) and then you never need > to deal with the "cache" per se anyways.
Bang on - they will barley ever change. Certainly for this phase they wont change at all. Later I could build an admin control that flushes the cache (or refreshes it etc) I guess. I'll try this in boot and see what happens > As for the Hibernate annotations, the only one that's strictly needed to > enable caching is > > @org.hibernate.annotations.Cache > > What annotations besides that one are you using, and which ones are > causing conflicts? There are quite a few that overlap with the JPA > standard annotation, so when I use them I usually make specific > imports. > There are several good articles out there on how to do this out on the web: > > http://www.gridshore.nl/2008/04/29/using-ehcache-and-verifying-that-i... > > In particular, it's important to differentiate between the entity > cache (enabled with the above annotation) and the query cache. It > sounds like you need the former. Cheers Derek, I'll give it a whirl and let you know how I get on :) Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
