[
https://issues.apache.org/jira/browse/WICKET-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Compagner updated WICKET-1128:
------------------------------------
Fix Version/s: 1.3.0-rc2
i guess this one is fixed now enough right?
we don't do it for you (we still could do that as a standard setting but i
don't care to much, it must be document right)
people can just call the localizers
public final void setEnableCache(boolean value)
now and the caching is disabled
> 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
> Fix For: 1.3.0-rc2
>
>
> 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.
