[
https://issues.apache.org/jira/browse/WICKET-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985758#action_12985758
]
Martin Grigorov edited comment on WICKET-3379 at 1/24/11 11:02 AM:
-------------------------------------------------------------------
Hm.
Now tinymce will expect url like : <filename>.ext?<epoch>, another component
library will expect <filename>-ts<epoch>.js and these two cannot be used
together in one application...
This is if the strategy is on application level, of course.
was (Author: mgrigorov):
Hm.
Now tinymce will expect url like : <filename>.ext?<epoch>, another component
library will expect <filename>-ts<epoch>.js and these two cannot be used
together in one application...
> Allow custom timestamp strategies for resources
> -----------------------------------------------
>
> Key: WICKET-3379
> URL: https://issues.apache.org/jira/browse/WICKET-3379
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Peter Major
>
> Currently the timestamp is appended to filenames if caching is enabled, like
> <filename>-ts<epoch>.<extension>
> During the process of migrating wicketstuff-tinymce to Wicket 1.5 it occured
> to me, that tinymce recognizes it's baseurl based on it's filename:
> https://github.com/wicketstuff/core/blob/master/jdk-1.5-parent/tinymce-parent/tinymce/src/main/java/wicket/contrib/tinymce/tiny_mce/tiny_mce_src.js#L53
> It would be nice if the cache naming strategy would be pluggable, so by
> implementing a class you could actually have resources like:
> <filename>.<extension>?<epoch>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
