using CachingResourceStreamLocator did the trick. thank you for help
regards
Armando
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-ResourceStreamLocator-performance-issue-tp3796815p3798549.html
Sent from the Users forum mailing list archive at Nabble.com.
-
It was not used in my setup at all.
The problem occurred when we wrote our own ResourceLocator and we extended
ResourceStreamLocator. (as wrote in Jira quickstart)
I'm trying to use CachingResourceLocator now.
Kind regards
Armando
--
View this message in context:
http://apache-wicket.18429
igorov [mailto:mgrigo...@apache.org]
>Sent: Thursday, 8 September 2011 5:45 PM
>To: users@wicket.apache.org
>Subject: Re: Wicket ResourceStreamLocator performance issue
>
>the fix will be in 1.5.1
>
>about the original issue in this thread: do you mean that
>CachingResourceStreamL
https://issues.apache.org/jira/browse/WICKET-4034 Jira issue
hope this helps.
I did not provide any patch because I think our workaround is not the way it
should be done.
Regards
Armando
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-ResourceStreamLocator-
the fix will be in 1.5.1
about the original issue in this thread: do you mean that
CachingResourceStreamLocator is slow or it is not in used in your
setup ?
it should be the default locator but maybe you replaced it
On Thu, Sep 8, 2011 at 9:31 AM, armandoxxx wrote:
> thank you for your reply
> i
thank you for your reply
is it fixed in final release (since I saw a final release was made
yesterday) or just in trunk ?
regards
Armando
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-ResourceStreamLocator-performance-issue-tp3796815p3797981.html
Sent from
this one is fixed in trunk
-igor
On Wed, Sep 7, 2011 at 10:14 PM, armandoxxx wrote:
> Another question.
>
> Is it normal that onAfterRender() methods gets called several times for each
> component ?
>
> Regards
>
> Armando
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.
Another question.
Is it normal that onAfterRender() methods gets called several times for each
component ?
Regards
Armando
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-ResourceStreamLocator-performance-issue-tp3796815p3797892.html
Sent from the Users fo
Please give me time till weekend cause I'm really busy. I'll write it then !
Kind regards
Armando
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-ResourceStreamLocator-performance-issue-tp3796815p3797889.html
Sent from the Users forum mailing list archive at
Next question: what did you change in your version to make it faster ?
Create a ticket with the patch ;-)
On Wed, Sep 7, 2011 at 11:19 PM, armandoxxx wrote:
> Sorry man .. forgot to mention version we're using is 1.5 RC7
>
> Regards
>
> Armando
>
> --
> View this message in context:
> http://apa
Sorry man .. forgot to mention version we're using is 1.5 RC7
Regards
Armando
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-ResourceStreamLocator-performance-issue-tp3796815p3797143.html
Sent from the Users forum mailing list archive at Nabble.com.
---
For which version of Wicket we are talking about ?
In 1.5 there is CachingResourceStreamLocator which is setup by default.
On Wed, Sep 7, 2011 at 9:01 PM, armandoxxx wrote:
> Hi
>
> We found serious performance issue costing aprox. 1 sec per request in
> ResourceStreamLocator.
>
> these are the r
12 matches
Mail list logo
