You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "bernard (JIRA)" <ji...@apache.org> on 2013/04/16 21:01:17 UTC
[jira] [Commented] (WICKET-4604) Improve Wicket code to not use
static caches
[ https://issues.apache.org/jira/browse/WICKET-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633193#comment-13633193 ]
bernard commented on WICKET-4604:
---------------------------------
A simple test case is to have an exception in Application#init() then re-deploy the app with the code fixed.
Then in Application#setName() Wicket crashes with IllegalStateException("Application name can only be set once.")
because of private static final Map<String, Application> applicationKeyToApplication
> Improve Wicket code to not use static caches
> --------------------------------------------
>
> Key: WICKET-4604
> URL: https://issues.apache.org/jira/browse/WICKET-4604
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5.7
> Reporter: Martin Grigorov
>
> We need to check Wicket code for any static fields which may cause problems when Wicket jars are put in Web container's shared libraries folder.
> For example caches implemented with static fields should be reworked to use Application's metadata.
> See http://markmail.org/thread/kd2anekvs4xlm4q4
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira