[
https://issues.apache.org/jira/browse/WICKET-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540245
]
Juergen Donnerstag commented on WICKET-1128:
--------------------------------------------
Not sure I understand all your comments.
1) new resource being added, such as new component etc.? I don't think this is
true, since it is a cache. What happens though is that Wicket remembers that no
properties file was found and doesn't check that anymore later on. It does only
check if a file has been changed. This need to be improved. agreed.
2) not sure what you mean. If a property has been changed and that the new
version will be used => the most up to date version. I guess the problem you
are referring is the one mentioned in 1)
3) see 1
4) Not sure I agree. If new properties files got detected, than the problem
would be solved. Disabling caching means the potential of finding problems with
caching s delayed until deployed. I rather find bug early.
To me it all comes down to what I mentioned in 1). And until we solved that
problem we may extend Localizer with a simple flag to disable caching.
Juergen
> Option not to use localizer cache in development mode.
> ------------------------------------------------------
>
> Key: WICKET-1128
> URL: https://issues.apache.org/jira/browse/WICKET-1128
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 1.3.0-beta4
> Environment: All
> Reporter: Sebastiaan van Erk
> Assignee: Juergen Donnerstag
>
> I was wondering if I could somehow turn off caching of the localizer in
> development mode (from the current source it doesn't look like it).
> The reason I ask is because now the cache is only flushed if a resource that
> is being watched is changed. However:
> * if you add a new properties file for a page or component after you already
> rendered the page once the cache is not cleared and it keeps finding the
> key=null entry in the cache.
> * if you add your own database string resource loader, the cache is never
> flushed at all.
> I know I can add a link to flush the localizer cache if and only if we're in
> development mode, but I think a Settings options could be nice to just turn
> off caching (my laptop is fast enough, I really don't care if it tries to
> resolve all the labels all the time).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
