When passivation is set to false, changes in POJO are not
passivated . What is missing?
Class implements Serializable ---- not replicable .
--------------------------------------------------------
Object rc = cacheManager.find( cacheKey );
//modify rc
rc.setDate(date);
Will the above change passivated to file system (FileCache
laoder is configured) on its own or do I need to detach and attach the object
again here.I am not seeing the changes passivated to secondary cache . Is the
below code required?
//cacheManager.detach(cacheKey)
//cacheManager.attach(cacheKey)
-----------------------------------------------------------------------
<!-- Cache
Loader configuration block -->
<attribute name="CacheLoaderConfig">
<config>
<!-- if passivation is true, only the first cache
loader is used; the rest are ignored -->
<!-- passivation should be false to retain the data
in secondary cache otherwise node will be deleted after loading to the memery
-->
<passivation>false</passivation>
<!-- comma delimited FQNs to preload -->
<!-- <preload>/ASOF_POSITION</preload>
-->
<shared>false</shared>
<!-- we can now have multiple cache loaders, which get
chained -->
<cacheloader>
<class>org.jboss.cache.loader.FileCacheLoader</class>
<properties>
location=e:/trash/jbosscache
</properties>
<!-- whether the cache loader writes are asynchronous -->
<async>true</async>
<!-- if set to true, purges the contents of this cache loader
when the cache starts up.
Defaults to false. -->
<purgeOnStartup>false</purgeOnStartup>
<!-- only one cache loader in the chain may set
fetchPersistentState to true.
An exception is thrown if more
than one cache loader sets this to true. -->
<fetchPersistentState>true</fetchPersistentState>
<!-- determines whether this cache loader ignores writes -
defaults to false. -->
<ignoreModifications>false</ignoreModifications>
</cacheloader>
</config>
</attribute>
Regards,
The Rohatyn Group,
212-984-3512.