On 8/9/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> As for the error-flow, and I don't really see why:
>
> try {
> ...query the database and build the provider and dataview
> } catch (SQLException e) {
> feedback.error("Very bad things happened");
> // What to do here??
> }
>
> should generate a different component structure rather than an error page.
> Eelco
Say that I want to show the page anyway since it might contain other
components that work. My requirements could very well be: A feedback
message saying that part of the page couldn't be rendered, remove the
faulty component (or replace it with a panel containing an error
description) and draw everything else.
So I tried to implement error handling in my data provider. It returns
an empty collection so nothing breaks but I do not get to see any
feedback messages in my feedback panel at the top of the page.
Probably because that component is already rendered when my
dataprovider is invoked.
So, now I'm overriding onAttach to get all my data which works nicely :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
