> Oh yeah, I did not really think this that deep. I was more concerned
> about situations that occur at the UI level only.
> Consider a case in which an admin is using multiple tabs in the
> browser, keeps a list of layers in one, removes one layer in the
> other, clicks on the same layer in the f
Justin Deoliveira ha scritto:
> I think it is a good idea for sure, but the trick is always how to do
> throw exceptions at the "service level" that can 1) be usable by the ui
> for useful error reporting and 2) not depend on any specific ui classes.
>
> Providing a hook at the UI level for exce
On Mon, Mar 16, 2009 at 12:22 PM, Andrea Aime wrote:
> Hi,
> wondering if anyone looked in consistent and decent looking
> error reporting for the Wicket UI, in particular for those
> errors that are not recoverable.
> Consider this fragment of code:
>
> CoverageStoreInfo cstore = (CoverageStoreIn
I think it is a good idea for sure, but the trick is always how to do
throw exceptions at the "service level" that can 1) be usable by the ui
for useful error reporting and 2) not depend on any specific ui classes.
Providing a hook at the UI level for exceptions seems like the easy
part. The ha
Hi,
wondering if anyone looked in consistent and decent looking
error reporting for the Wicket UI, in particular for those
errors that are not recoverable.
Consider this fragment of code:
CoverageStoreInfo cstore = (CoverageStoreInfo) store;
CatalogBuilder builder = new CatalogBuilder(getCatalog()
