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
> "..".
OK, that one is solved, too. After replacing the Application
used in this test by the one created to solve the
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() /
> ThreadContext.setRequestC
On Fri, Sep 6, 2013 at 7:41 PM, Martin Dietze 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, however the
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'
Hi,
On Fri, Sep 6, 2013 at 3:36 PM, Martin Dietze 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 with some ex
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 with some exception inside Wicket.
Since I am rather unfamiliar with the wicket
