]
Manik Surtani closed JBCACHE-562.
---------------------------------
Resolution: Rejected
I don't think we should disable cache loaders based on the class being configured
being an empty string or a null.
Disable cache loader when no cacheloader class is specified
-----------------------------------------------------------
Key: JBCACHE-562
URL:
http://jira.jboss.com/jira/browse/JBCACHE-562
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Ben Wang
Assigned To: Manik Surtani
Priority: Minor
Fix For: 2.0.0.GA
In 1.3, we support a new form of cacheloader config. However, it is incovenient to
disable the cache loader (previously all we need is to specify cacheloaderclass to empty).
We should also support this kind of semantics so we can disable it easily. I propose when
do createcacheloader, we also check whether the class name is there or not to decide
whether to go ahead. If not, we simply log an info message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: