That is a bummer, cause global configuration setup needs to be done before cache starts, so no chance of adding Externalizers with the Cache instance already created. IMHO it will also make everything more complicated with the usual model of getting a cache already pre-configurated from manager, like done currently in AS5 for JBC, and then applying more configuration. Well, will need to rework the whole startup model. The DCM getStatus() returns RUNNING after getting cache. -- Eduardo .............................................. http://emmartins.blogspot.com http://redhat.com/solutions/telco On Thu, Feb 10, 2011 at 9:33 AM, Galder Zamarreño <galder(a)redhat.com&gt; wrote: > Yeah, that's expected cos you can't get a cache without starting it. We're likely to provide such functionality in the near future (https://issues.jboss.org/browse/ISPN-627) > > In the code that you showed, could you check one thing? If you get a DefaultCacheManager without starting it, after getting the cache, what's DCM returning to getStatus() method call? > > On Feb 9, 2011, at 4:45 PM, Eduardo Martins wrote: > >> cache = new DefaultCacheManager(globalConfiguration, >> configuration, false).getCache() >> >> The cache is returned already started, is this the expected behavior? >> >> -- Eduardo >> .............................................. >> http://emmartins.blogspot.com >> http://redhat.com/solutions/telco > > -- > Galder Zamarreño > Sr. Software Engineer > Infinispan, JBoss Cache > >