[jira] [Commented] (WICKET-5590) Add a method to clear the cache of CachingResourceVersion
[ https://issues.apache.org/jira/browse/WICKET-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001739#comment-14001739 ] ASF GitHub Bot commented on WICKET-5590: Github user martin-g commented on a diff in the pull request: https://github.com/apache/wicket/pull/73#discussion_r12797692 --- Diff: wicket-core/src/main/java/org/apache/wicket/request/resource/caching/IResourceCachingStrategy.java --- @@ -71,4 +71,10 @@ * @param response */ void decorateResponse(AbstractResource.ResourceResponse response, IStaticCacheableResource resource); + + /** +* Clears any stateful information +*/ + void clearCache(); --- End diff -- This addition of a new method to a public interface makes this change applicable only to Wicket 7.x. I see the PR is actually against `master`. Add a method to clear the cache of CachingResourceVersion - Key: WICKET-5590 URL: https://issues.apache.org/jira/browse/WICKET-5590 Project: Wicket Issue Type: New Feature Components: wicket Affects Versions: 6.15.0 Reporter: Fridolin Jackstadt Priority: Minor Since our Application supports to change resouces content at runtime of wicket application, we need a mechanism to invalidate the resource version cache. The implementation is easy and very useful for us, and we will make a pull request for that. We would be very happy to find it in one of the next releases. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (WICKET-5590) Add a method to clear the cache of CachingResourceVersion
[ https://issues.apache.org/jira/browse/WICKET-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001746#comment-14001746 ] ASF GitHub Bot commented on WICKET-5590: Github user asfgit closed the pull request at: https://github.com/apache/wicket/pull/73 Add a method to clear the cache of CachingResourceVersion - Key: WICKET-5590 URL: https://issues.apache.org/jira/browse/WICKET-5590 Project: Wicket Issue Type: New Feature Components: wicket Affects Versions: 6.15.0 Reporter: Fridolin Jackstadt Assignee: Martin Grigorov Priority: Minor Fix For: 7.0.0-M2 Since our Application supports to change resouces content at runtime of wicket application, we need a mechanism to invalidate the resource version cache. The implementation is easy and very useful for us, and we will make a pull request for that. We would be very happy to find it in one of the next releases. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (WICKET-5590) Add a method to clear the cache of CachingResourceVersion
[ https://issues.apache.org/jira/browse/WICKET-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998576#comment-13998576 ] ASF GitHub Bot commented on WICKET-5590: GitHub user frido37 opened a pull request: https://github.com/apache/wicket/pull/73 WICKET-5590 Add a method to clear the cache of CachingResourceVersion You can merge this pull request into a Git repository by running: $ git pull https://github.com/frido37/wicket master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/wicket/pull/73.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #73 commit 1274ea5673fe5aa02ac54f40e3635050a8d67e31 Author: Fridolin Jackstadt fridolin.jackst...@lindenbaum.eu Date: 2014-05-15T08:22:54Z WICKET-5590 Add a method to clear the cache of CachingResourceVersion Add a method to clear the cache of CachingResourceVersion - Key: WICKET-5590 URL: https://issues.apache.org/jira/browse/WICKET-5590 Project: Wicket Issue Type: New Feature Components: wicket Affects Versions: 6.15.0 Reporter: Fridolin Jackstadt Priority: Minor Since our Application supports to change resouces content at runtime of wicket application, we need a mechanism to invalidate the resource version cache. The implementation is easy and very useful for us, and we will make a pull request for that. We would be very happy to find it in one of the next releases. -- This message was sent by Atlassian JIRA (v6.2#6252)
