I want to mention that the exception message in the first case was: "Markup of type 'html' for component 'MyForm' not found".
In other words, the word "invalid" is not added to the message. This is very misleading.

Francis

On 9/16/05, Francis Amanfo <[EMAIL PROTECTED]> wrote:
Hi,

Wicket is a great framework but IMO one place I think its currently not doing a very good job is Runtime exception reporting. Coming from Tapestry, I can say that it is one place Tapestry does quite well and hope Wicket can catch up on that front.
Now I'll go into details of where my frustration lies.

I had a markup (MyForm.html) which by accident and erroneously contained two id names'. Example <form id="myform" id="myform">. Note that I'm not talking about "wicket:id" but just plain html id. Wicket generated the following runtime exception:

"Markup of type 'html' for component 'MyForm' not found or invalid Enable debug messages for wicket.util.resource.Resource to get a list of all filenames tried:"
Ok, I agree it was an invalid markup.But can't wicket catch and throw this specific error (like currently what gets reported when a markup is not XHTML compatible) instead of the more generic "markup not found or invalid" message?

Another issue I have is runtime exception messages reported when the component class is trying to render a component that has not been declared in the corresponding markup. That error is often:
"wicket.WicketRuntimeException: The component(s) below failed to render:"
I think the life of Wicket newbies could be made a bit easier if for instance a message like "Possible cause: Component class is trying to render a component that has not been declared in the markup" is added. IMHO, this is more straight forward and could save a lot of debugging time.

What do you guys think about these?

Regards,

Francis


Reply via email to