Hi all, With Wicket 1.5, resource loading is no longer cached in development mode. This causes extreme slowdowns in our application. Pages that used to take 10-15ms, now take up to 10 seconds to load. This seems to be caused by the fact that ResourceStreamLocator checks for the existence of files way too often. Yourkit counted 255k calles to File.exists for a single page load. I must admit that this is partly caused by our extension to ComponentStringResourceLoader, which adds many calls to the resource loader.
For now, we 'fixed' this by enabling caching in development mode, but wouldn't it be possible to use the modification watcher to invalidate the cache in development mode, rather than disabling the cache entirely? Best regards, Emond Papegaaij
