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

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-4034.
-------------------------------------

    Resolution: Not A Problem

> calls to ResourceStreamLocator.locate() are causing serious performance issues when locating wicket resources
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-4034
>                 URL: https://issues.apache.org/jira/browse/WICKET-4034
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-RC7
>         Environment: Linux MInt 11 Katya, JDK 1.6.0_26
>            Reporter: Armando Ota
>              Labels: ResourceStreamLocator, performance, wicket
>         Attachments: wicket-issue-4034.zip
>
>
> 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)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira