Back port resource caching with component provided resource cache key ---------------------------------------------------------------------
Key: WICKET-224 URL: https://issues.apache.org/jira/browse/WICKET-224 Project: Wicket Issue Type: Improvement Components: wicket Reporter: Eelco Hillenius Fix For: 1.3 In 2.0 resource caching is overridable up to the component level, including providing a resource cache key for the resource stream. By providing a null resource cache key, you can achieve that the resource stream is never cached, which is something you need when you want to use a dynamic resource stream that can change over requests/ sessions. This is a request to back port that functionality, so that truly dynamic templates can be used in Wicket 1.3 as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira