[
https://issues.apache.org/jira/browse/WICKET-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542402
]
Sebastiaan van Erk commented on WICKET-1128:
--------------------------------------------
Well, the caching is fixed, but that was not really the issue anymore (or the
reason why it was reopened).
The reason it was reopened is because once the property file resource is found,
it is cached, and only THAT resource is cached. If the locator changes its mind
about the stream it should be using, then the new stream is never loaded. (See
also the linked issue 1142). Thus adding a new propertyfile
MyPage_en.properties will not see the changes if a BasePage.properties existed
and was already loaded when viewing MyPage.
However, since what remains is pretty much an exact duplicate of 1142 but then
for property files instead of markup files, and the solution is probably
exactly the same as well, so I think its probably best to close this one and
just keep 1142. Only other difference between the two bugs is their severity
(minor vs major). It seems kind of minor (it's a devel mode only thing, and
just saves some restarts), but especially with the localization it feels kind
of buggy the way it is now.
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
> 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.
