Page History

...

ImageMap was deprecated in 1.4.11 and in 1.5 it was replaced with ClientSideImageMap component

getResourceSettings().setAddLastModifiedTimeToResourceReferenceUrl() has been replaced

...

by IResourceCachingStrategy

Wicket 1.5 has a new feature called "resource caching strategy".

There are several implementation of the interface

org.apache.wicket.request.resource.caching.IResourceCachingStrategy

which provide different ways of caching your resources (e.g. CSS, javascript, images). Also it's quite easy to implement your own strategy.

The default caching strategy is

org.apache.wicket.request.resource.caching.FilenameWithTimestampResourceCachingStrategy

See the javadoc of the class for details.

It merges the last modified timestamp of the resource into the base resource name. For a good description of this style of caching see With https://issues.apache.org/jira/browse/WICKET-3028 and https://issues.apache.org/jira/browse/WICKET-3021 this method was replaced. The timestamp, which previously was added as a query parameter to the resource url is now part of the file's basename (the name part before the extension). This has several advantages and gives you best possible caching support. See for example chapter

Use fingerprinting to dynamically enable caching

...

http://code.google.com/intl/de-DE/speed/page-speed/docs/caching.html

You can set your own caching strategy with

getResourceSettings().setCachingStrategy(...)

To disable caching altogether (e.g. for performance comparisons) use

The feature is enabled by default so unless you want to disable it with getResourceSettings().setUseTimestampOnResources(boolean) or query its state with setCachingStrategy(getResourceSettings().getUseTimestampOnResources() you usually don't have to care about it at all. Timestamping only works when the ResourceReference supports a last modified timestamp and returns a non-null timestamp for method ResourceReference.getLastModified(). This is always true for package resources and wicket:link.setCachingStrategy(org.apache.wicket.request.resource.caching.NoOpResourceCachingStrategy.INSTANCE))

Inter-component events

Wicket 1.5 offers a simple, yet flexible, way for component to communicate with each other in a decoupled manner. The two major interfaces that facilitate this are:

...