EhCache is able to init cache managers in singleton mode and it's singleton-ness is different to your server layer/transfers singleton- ness.
You could use this to manage what you want. You might need to tweak transfer's ehCache provider classes to achieve this, but it's possible. dave On Sep 16, 11:36 pm, Robert Rawlins <rob...@supporttime.com> wrote: > Hello Guys, > > I've got an application using Transfer along with MG and CS that runs a > fairly substantial cache on it, which is really very important to > performance. > > One thing I've been finding ever so frustrating is that if I make a small > change to a service layer object, a bug fix for instance and have to reinit > the application, transfer is also reinited and all the cached objects that > have accumulated are lost. > > I'm looking for a decent strategy to help maintain the cache in instances > like this, so we don't have degraded performance for hours or days after a > small fix to a single object. > > Can anyone offer their experiences and approaches? > > Thanks. > > Robert -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to transfer-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en