Eelco reminded me that loading markup resource streams doesn't work properly yet if a custom markup cache key is provided. I changed the code, it should be backportable to 1.3, but the API has slightly changed. Instead of MarkupContainer.newMarkupResourceStream() returning MarkupResourceStreamLookupResult, there are now 2 new interfaces IMarkupResourceStreamProvider and IMarkupCacheKeyProvider. Both have just one method. Default implementation exists and are used by MarkupCache by default, and can be subclassed. If the component implements any of the two interfaces there respective methods are called instead of the default ones. What do you think?
Juergen ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
