cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pier Fumagalli (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COCOON-1131) Caching inoperative in modular DatabaseAction
Date Tue, 25 Oct 2005 15:45:56 GMT
     [ http://issues.apache.org/jira/browse/COCOON-1131?page=all ]

Pier Fumagalli updated COCOON-1131:
-----------------------------------

    Bugzilla Id:   (was: 28495)
      Component: Blocks: Databases
                     (was: Blocks: (Undefined))
    Description: 
In org.apache.cocoon.acting.modular.DatabaseAction, the implemented query 
caching is inoperative.

In the processTable() method a new
LookUpKey is created for every request, and since the equals/hashKey methods are
not overriden in LookUpKey, this means that the getQuery() method will be called 
for all requests and no caching is used, since the HashMap get will always 
return null.

....Andrzej

  was:
In org.apache.cocoon.acting.modular.DatabaseAction, the implemented query 
caching is inoperative.

In the processTable() method a new
LookUpKey is created for every request, and since the equals/hashKey methods are
not overriden in LookUpKey, this means that the getQuery() method will be called 
for all requests and no caching is used, since the HashMap get will always 
return null.

....Andrzej


> Caching inoperative in modular DatabaseAction
> ---------------------------------------------
>
>          Key: COCOON-1131
>          URL: http://issues.apache.org/jira/browse/COCOON-1131
>      Project: Cocoon
>         Type: Bug
>   Components: Blocks: Databases
>     Versions: 2.1.4
>  Environment: Operating System: All
> Platform: All
>     Reporter: Andrzej Taramina
>     Assignee: Cocoon Developers Team

>
> In org.apache.cocoon.acting.modular.DatabaseAction, the implemented query 
> caching is inoperative.
> In the processTable() method a new
> LookUpKey is created for every request, and since the equals/hashKey methods are
> not overriden in LookUpKey, this means that the getQuery() method will be called 
> for all requests and no caching is used, since the HashMap get will always 
> return null.
> ....Andrzej

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message