[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-562) Disable cache loader when no cacheloader class is specified

[Brian Stansberry (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCACHE-562?page=comments#action_12347643 ] 
            
Brian Stansberry commented on JBCACHE-562:
------------------------------------------

Not quite as simple with the pojo-based configuration in 2.0, since the cacheloader class is an inherent property of the typed config object.  The config object should probably have an "enabled" property.

The "empty class" idea could still work for parsing 1.x-style configs, though. If class is empty, parser doesn't create the config pojo, and thus no cacheloader is created. 

> 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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira