Hi all,
Thank you very much for all the suggestions.
I agree that the slowness is because of Spring context initialized multiple
times.
Ours is a multi module maven application and what I have seen is the
context being initialized at least once per module because of new beans in
every module.
The
Hi,
*Background:*
I'm trying to mount 404 page to my Wicket project.
I found confluence page wchich explains how to do it using web.xml
(https://cwiki.apache.org/confluence/display/WICKET/Error+Pages+and+Feedback+Messages#ErrorPagesandFeedbackMessages-HTTPErrorPages)
but my application uses W
Hello,
I guess my last mail was to complex so I'll try to simplify it:
Why children's "onRemove" method is not called when "setResponsePage" is
called?
As I've written previously - manually invoking "page.removeAll()" works
but shouldn't it be called automatically?
Jarek
On 09.02.2018 11:49
Probably you're initializing your application for each test, so you
should look into speeding that up or eliminating it all together (just
once for the whole suite)
Martijn
On Mon, Feb 12, 2018 at 5:05 AM, James Selvakumar wrote:
> Hi,
>
> We have a Wicket 7.x application which uses a Spring/Hi