Maintaining Cache w/ Framework Reload

[Robert Rawlins]

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

[Pedro Bezunartea López]

Hi again, Robert,

My experience is that unless you only modify the views, you need to reinit the framework, and loose cached objects... honestly, I don't see how you could keep objects cached that may have changed their behaviour when you modify their code. :P

Cheers,

Pedro.

[Dave]

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