tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Klein (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TAP5-1953) Does the cache for resolved page class names grow indefinetly?
Date Thu, 07 Jun 2012 22:30:23 GMT
Carsten Klein created TAP5-1953:
-----------------------------------

             Summary: Does the cache for resolved page class names grow indefinetly?
                 Key: TAP5-1953
                 URL: https://issues.apache.org/jira/browse/TAP5-1953
             Project: Tapestry 5
          Issue Type: Question
          Components: tapestry-core
    Affects Versions: 5.3.3
            Reporter: Carsten Klein


Having implemented a decorator for the ComponentClassResolver service, I noticed that my advises
and the delegates thereof will be called only during initial resolve of the page class name
for a given request path.

I wonder if the cache, which prevents subsequent calls to the custom resolver between requests,
does grow indefinitely, and if so, would it be possible to change it so, as to not consume
all of the available memory in situations of both high load and indefinite numbers of available
request paths?

Also, I have been unable to find the class/method responsible for caching the results from
my custom resolver to this point. Could you please point me to where I may find the caching
logic?

TIA and keep up the great work!

-- Carsten

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message