followup just so in case someone else might find this useful.
the wicket, out of the box css url handling works for resources in the
classpath. it will not work for stuff you might have tucked away in the
webapp directory which was my case.
for those cases i added a custom header response decorator in the
application.
protected void validateInit() {
super.validateInit();
setHeaderResponseDecorator( CachingStrategyDecoratingHeaderResponse.
createHeaderResponseDecorator());
}
its' responsibility was to append a suffix in the render??Reference methods
that took a URL parameter.
class CachingStrategyDecoratingHeaderResponse extends
WiQueryDecoratingHeaderResponse {
public void renderCSSReference(String url) {
super.renderCSSReference(url+"?VERSION="+someNumber);
}
etc....
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Appending-to-CSS-url-to-prevent-caching-tp4652508p4653226.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
