Page History

...

Note that resource finder (IResourceFinder implementations) are still being used. This detail has not been changed.H4.

Custom resource loading

In Wicket 1.2 you could override method newMarkupResourceStream from MarkupContainer to provide a custom resource stream for loading the component's markup. The new way of letting markup containers provide custom markup is to let them implement interface IMarkupResourceStreamProvider and implement it's method getMarkupResourceStream. Additionally, a new feature is that you can provide your own markup cache key, which is used in the MarkupCache class. The only real use case for that is to let a markup container return a cache key that is null, in which case the resource won't be cached, causing Wicket to get call getMarkupResourceStream everytime the component's markup is requested. A use case for that is when you have dynamic markup (e.g. from a database) that is request/ session dependent. To achieve this, let your markup container also implement IMarkupCacheKeyProvider and let method getCacheKey return null.

...

to check for non-serializable objects yourself. You could do this for instance in a custom session store implementation.

Palette component in wicket-extensions now has default CSS.

You can revert this back to 1.2.x behaviour by overriding getCSS() and returning null.