[jboss-dev-forums] [Design of JBossCache] - Re: JBoss Cache Public API

[bstansberry@jboss.com]

"manik.surtani at jboss.com" wrote : Re: lifecycle, don't people find it useful to create a cache, then set up stuff, such as register classloaders for regions, register listeners, etc., and then start?
  | 
  | Or should create() really be an initial state that is attained by calling CacheFactory.createCache()?

Yeah, I think that's the idea.

anonymous wrote : And then what about stop() and destroy()?  Does it not make sense that a cache, once stopped, could be started again - which implies that internal components should not be cleaned up/released?

Yes, absolutely.

anonymous wrote : In which case isn't a destroy() necessasry to actually release resources and clean up?

Depends on whether they require some cleanup beyond garbage collection.  Sounds like that's the thing to investigate.


Not sure if I was clear in my previous comment on this.  Not saying we should definitely drop the 4 step lifecycle; just that the original reason for it no longer really applies, so worth looking into it.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158380#4158380

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158380