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

Brian Stansberry (JIRA) jira-events at jboss.com
Fri Nov 24 03:17:41 EST 2006


     [ http://jira.jboss.com/jira/browse/JBCACHE-562?page=all ]

Brian Stansberry updated JBCACHE-562:
-------------------------------------

        Summary: Disable cache loader when no cacheloader class is specified  (was: Disable cache loader when no classloader class is specified)
    Description: 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.  (was: In 1.3, we support a new form of classloader 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.)

> 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

        



More information about the jboss-jira mailing list