You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (Commented) (JIRA)" <ji...@apache.org> on 2012/03/20 10:31:40 UTC
[jira] [Commented] (WICKET-1373) cache created proxy classes
[ https://issues.apache.org/jira/browse/WICKET-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233326#comment-13233326 ]
Martin Grigorov commented on WICKET-1373:
-----------------------------------------
What exactly should be improved here ?
JDK proxy classes are already cached - java.lang.reflect.Proxy#newProxyInstance() calls java.lang.reflect.Proxy#getProxyClass() which supports caching.
I'm not sure what is the state in CGLIB.
> cache created proxy classes
> ---------------------------
>
> Key: WICKET-1373
> URL: https://issues.apache.org/jira/browse/WICKET-1373
> Project: Wicket
> Issue Type: Sub-task
> Reporter: Igor Vaynberg
> Assignee: Johan Compagner
>
> we can cache the created proxy class and simply give each instance a
> new handler...
> -igor
> On Tue, Feb 26, 2008 at 10:26 AM, James Carman
> <ja...@carmanconsulting.com> wrote:
> > Have you tried this out using load testing? You are creating a new
> > class every time you create a model. Have you run out of permgen
> > space?
--
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