Philip,
To be fair, I think the problem has more to do with my ignorance of
Wicket than a problem with the error message. I'm a new user, but am
getting better. The error message did give me an idea of what was going
on; the message in the mailing list just gave me a concrete way to fix it.
Tha
You should just say, "Use markup inheritance instead." in the error message.
On 8/4/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> yes I agree, it seems to be a common problem for people migrating from
> 1.0 to 1.1, which is why the exception message is like
>
> "If the root exception says s
yes I agree, it seems to be a common problem for people migrating from
1.0 to 1.1, which is why the exception message is like
"If the root exception says something like "A child with id '_header'
already exists" then you most likely forgot to override autoAdd() in
your bordered page component."
M
Should the exception perhaps include a message letting people know about this potential pitfall?
Seems like a common problem...On 8/3/05, Philip A. Chapman <[EMAIL PROTECTED]> wrote:
To anyone that comes across the same problem, I found the solution here:http://sourceforge.net/mailarchive/message.
To anyone that comes across the same problem, I found the solution here:
http://sourceforge.net/mailarchive/message.php?msg_id=12398585
Thanks,
Philip A. Chapman wrote:
> Everyone,
>
> I have been using Wicket 1.0.1. The application worked fine using
> Firefox. However, I ran across the infin
Everyone,
I have been using Wicket 1.0.1. The application worked fine using
Firefox. However, I ran across the infinite loop bug when using
RedirectPage and IE. I upgraded to 1.1.b2 hoping that it had been
fixed. After upgradeing, however, on a page that I have that uses the
PageableListView a
