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 (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/25 17:51:28 UTC
[jira] [Resolved] (WICKET-1373) cache created proxy classes
[ https://issues.apache.org/jira/browse/WICKET-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-1373.
-------------------------------------
Resolution: Not A Problem
Assignee: (was: Johan Compagner)
JDK Proxy classes are cached by default.
CGLIB also caches the classes by default (we do not use Enhancer#setUseCache(false) in LazyInitProxyFactory).
Please comment if I understood wrongly the task and I'll reopen it again.
> 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
>
> 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