[WICKET-4034] calls to ResourceStreamLocator.locate() are causing serious performance issues when locating wicket resources

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.5-RC7
• Component/s: wicket
• Labels: ResourceStreamLocator performance wicket
• Environment: Linux MInt 11 Katya, JDK 1.6.0_26
• Assignee: Unassigned
• Reporter: Armando Ota
• Created: 08/Sep/11 08:05
• Updated: 08/Sep/11 10:46
• Resolved: 08/Sep/11 10:10

Description

Calls to ResourceStreamLocator.locate() method for wicket resources (check bellow for searched resources) is causing serious performace issues.

Resources searched:
org/apache/wicket/markup/html/wicket-event_en_US.js
org/apache/wicket/markup/html/wicket-event_en.js
org/apache/wicket/markup/html/wicket-event.js
org/apache/wicket/ajax/wicket-ajax_en_US.js
org/apache/wicket/ajax/wicket-ajax_en.js
org/apache/wicket/ajax/wicket-ajax.js

Check quickstart for example (check log):
run command: "mvn clean jetty:run" to see original performance (on my machine home page renders in 239 ms)
run command "mvn -Dworkaround=true clean jetty:run" to see the performance with workaround (on my machine home page renders in 60ms)