On 8/7/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> in 1.2 you cannot call error/info/etc from component's constructor because
> you havent added that component to the page yet. in 1.3 it just works.
Indeed.
I was under the false impression that this function worked on regular
deployment, but th
in 1.2 you cannot call error/info/etc from component's constructor because
you havent added that component to the page yet. in 1.3 it just works.
-igor
On 8/7/07, Gabor Szokoli <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm using wicket 1.2, and use the WicketTester startPage(...) method
> in a unit
Hi,
I'm using wicket 1.2, and use the WicketTester startPage(...) method
in a unit test.
(In fact there's nothing else in it, I just want to test if the markup
matches the component hierarchy.)
Problem is, a component on the page uses its error(...) method to
display its dissatisfaction with the m
