On Sat, September 07, 2013, Martin Grigorov wrote:
com.mycompany.request.WicketContainerChecker.onInstantiation(WicketContainerChecker.java:48)
What is this doing ?
Does it start a new thread by chance ?
Or doing something like: ThreadContext.detach() /
On Mon, September 09, 2013, Martin Dietze wrote:
No, nothing of that kind. It's just a helper to make sure noone
uses Ajax on components which are added to the markup as
wicket:container wicket:id=../wicket:container
OK, that one is solved, too. After replacing the Application
used in
On Fri, Sep 6, 2013 at 7:41 PM, Martin Dietze d...@fh-wedel.de wrote:
On Fri, September 06, 2013, Martin Grigorov wrote:
2. #testAddingAndSwitchingFields
you look at the wrong test
we cannot help you when we have the wrong source given
Yes, sorry, I picked the wrong stacktrace,
Hi,
On Fri, Sep 6, 2013 at 3:36 PM, Martin Dietze d...@fh-wedel.de wrote:
I am currently trying to repair some old tests (which I did not
even write myself) based on AbstractWicketTest and WicketTester.
At the moment all tests derived from AbstractWicketTest or using
TestNGWicketTester fail
On Fri, September 06, 2013, Martin Grigorov wrote:
2. #testAddingAndSwitchingFields
you look at the wrong test
we cannot help you when we have the wrong source given
Yes, sorry, I picked the wrong stacktrace, however they're all
identical anyway. The method 'testAddingAndSwitchingFields'
