Maybe we should consider expanding our exception hierarchy
a bit. Currently we only have the WicketRuntimeException and MarkupException.
Maybe we can introduce MarkupNotFoundException and MarkupInvalidException with
their own specialized messages. Sometimes the cause of the exception is so far
down it is hard to find or it simply gets cut off, im for putting the most
specific message into the exception's message instead of leaving it to the user
to find in the deepest cause.
-Igor
This "Markup not found" exception thing is extremely misleading and think needs addressing if Wicket is seriously aiming at going mainstream. In my early days of Wicket I struggled so much with it. It can happen because the markup really doesn't exist but also sometimes when there is an error in your markup that wicket can't really point to, in others words can't parse the xhtml. Only when Wicket can point to the error wil it tell you there is an error in your html by pointing directly to where the error is. I think the exceptions catching in wicket core could do better. If this is not considered to be addressed at the framework core, then I think we should start compiling scenarios from our own experiences when this exception was thrown. This could save newbies to Wicket a lot of frustrations and time.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francis Amanfo
Sent: Tuesday, October 25, 2005 2:40 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Markup not found
Francis
On 10/25/05, Nick Heudecker <[EMAIL PROTECTED]> wrote:I've been staring at this for hours, but can't figure out what would cause a "Markup not found" error when the markup does in fact exist at the correct location. What other error conditions could cause this problem? Thanks.
