[
https://issues.apache.org/jira/browse/WICKET-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540272
]
Sebastiaan van Erk commented on WICKET-1128:
--------------------------------------------
While I personally prefer a non-caching localizer on development mode, I can
understand the problem Juergen has with it.
You're going to get people who make their own database string resource loader,
and everything works find and dandy when they're in development mode. Then when
they deploy, suddenly the strings don't update like they're expecting. They're
going to complain that it's broken in deployment mode, and there's going to be
a JIRA saying they want it back the old way. :-)
I think if you're doing fancy stuff like making your own string resource
loaders you can also be expected to do something like the following for
development mode:
if (!isDeployment()) {
getResourceSettings().setLocalizer(new Localizer() {
@Override
protected void putIntoCache(String cacheKey,
String string) {
// Do not cache.
}
});
}
It's not much code, the only hassle for the developer is figuring out HOW to do
this...
Regards,
Sebastiaan
> 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.
