You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Carsten Klein (JIRA)" <ji...@apache.org> on 2012/06/08 00:30:23 UTC
[jira] [Created] (TAP5-1953) Does the cache for resolved page class
names grow indefinetly?
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
[jira] [Updated] (TAP5-1953) Does the cache for resolved page class
names grow indefinetly?
Posted by "Carsten Klein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Klein updated TAP5-1953:
--------------------------------
Comment: was deleted
(was: I forgot to add that as a workaround, one also has to use withId(...) when binding the service interface implementation classes. In that case, the object locator will return the correct implementation class.
)
> 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
[jira] [Commented] (TAP5-1953) Does the cache for resolved page
class names grow indefinetly?
Posted by "Carsten Klein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291389#comment-13291389 ]
Carsten Klein commented on TAP5-1953:
-------------------------------------
I forgot to add that as a workaround, one also has to use withId(...) when binding of the service interface implementation classes. In that case, the object locator will return the correct implementation class.
> 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
[jira] [Closed] (TAP5-1953) Does the cache for resolved page class
names grow indefinetly?
Posted by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiago H. de Paula Figueiredo closed TAP5-1953.
-----------------------------------------------
Resolution: Invalid
Please post questions to the Tapestry users mailing list: http://tapestry.apache.org/mailing-lists.html.
> 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
[jira] [Closed] (TAP5-1953) Does the cache for resolved page class
names grow indefinetly?
Posted by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiago H. de Paula Figueiredo closed TAP5-1953.
-----------------------------------------------
Resolution: Invalid
Please post questions to the Tapestry users mailing list: http://tapestry.apache.org/mailing-lists.html.
> 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
[jira] [Commented] (TAP5-1953) Does the cache for resolved page
class names grow indefinetly?
Posted by "Carsten Klein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291389#comment-13291389 ]
Carsten Klein commented on TAP5-1953:
-------------------------------------
I forgot to add that as a workaround, one also has to use withId(...) when binding of the service interface implementation classes. In that case, the object locator will return the correct implementation class.
> 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
[jira] [Comment Edited] (TAP5-1953) Does the cache for resolved
page class names grow indefinetly?
Posted by "Carsten Klein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291389#comment-13291389 ]
Carsten Klein edited comment on TAP5-1953 at 6/7/12 10:39 PM:
--------------------------------------------------------------
I forgot to add that as a workaround, one also has to use withId(...) when binding the service interface implementation classes. In that case, the object locator will return the correct implementation class.
was (Author: carsten.klein):
I forgot to add that as a workaround, one also has to use withId(...) when binding of the service interface implementation classes. In that case, the object locator will return the correct implementation class.
> 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
[jira] [Updated] (TAP5-1953) Does the cache for resolved page class
names grow indefinetly?
Posted by "Carsten Klein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Klein updated TAP5-1953:
--------------------------------
Comment: was deleted
(was: I forgot to add that as a workaround, one also has to use withId(...) when binding the service interface implementation classes. In that case, the object locator will return the correct implementation class.
)
> 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
[jira] [Comment Edited] (TAP5-1953) Does the cache for resolved
page class names grow indefinetly?
Posted by "Carsten Klein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291389#comment-13291389 ]
Carsten Klein edited comment on TAP5-1953 at 6/7/12 10:39 PM:
--------------------------------------------------------------
I forgot to add that as a workaround, one also has to use withId(...) when binding the service interface implementation classes. In that case, the object locator will return the correct implementation class.
was (Author: carsten.klein):
I forgot to add that as a workaround, one also has to use withId(...) when binding of the service interface implementation classes. In that case, the object locator will return the correct implementation class.
> 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