[
https://issues.apache.org/jira/browse/WICKET-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540254
]
Sebastiaan van Erk commented on WICKET-1128:
--------------------------------------------
Hi,
By 1) I mean adding any property files, either for the application, for a page,
or for a component. The cache is not cleared and the negative caching causes
the properties not to be found.
By 2) I mean that my experience in development mode in Wicket is that all
changes I make anywhere are immediately visible. I'm not saying this is an
official Wicket policy or anything, it's just the intuitional feel of things
that I have when using Wicket.
As far as the rest goes, I mostly agree. Fixing 1) would fix 3) for the
standard string resource loaders, and make the caching transparent in
development mode (for the standard string resource loader) fixing 2) as well.
As far as 4 goes, I don't really know which way I'm on that. I can see your
point about catching bugs early though I also feel it kind of goes against the
intuition of 2); I'd be perfectly happy if 1) is fixed now that I know how to
fix the caching issue for my database string resource loader. :-)
So I guess we're agreeing. Should I open a new JIRA issue for 1) or should we
just reopen this one?
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.
