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
t
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
Cool. For now I'd say just load it once, although you might want to make
your own object to manage it. You could easily make it a lazy var for now
and turn it into a synchronized def later if you need "flush" behavior.
Derek
On Tue, Sep 16, 2008 at 6:59 AM, Tim Perrett <[EMAIL PROTECTED]> wrote:
Sorry to drag this thread back up - I only just got back round to it
(its my hobby project)
WARN - No configuration found. Configuring ehcache from ehcache-
failsafe.xml found in the classpath: jar:file:/Users/timperrett/.m2/
repository/net/sf/ehcache/ehcache/1.5.0/ehcache-1.5.0.jar!/ehcache-
fa
On Tue, Sep 30, 2008 at 11:54 PM, Tim Perrett <[EMAIL PROTECTED]> wrote:
> Having an issue with ehcache.xml being picked up. The docs say that it
> need to be on the classpath - I've tried having it in META-INF, WEB-
> INF/classes/META-INF but yet nothing seems to work. It never gets
> picked up.
> IIRC, it needs to be at the top of the classpath, not under META-INF.
Good god, I must stop working at midnight my apologies! The brain
had obviously ceased functioning at that point!
--~--~-~--~~~---~--~~
You received this message because you are subscribed
