> 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 first... boom! > And "boom" it should be, but somehow controlled. > So far I threw IllegalArgumentExceptions or some other sort of > exception, was trying to figure out a better way to handle this. > Maybe we should just have the code redirect to a well known error > page that informs the user of what happened using an error key, > and that page then has a link to go back to the home page, > and space for a stack trace as well if we want. > The same page could be use as a generic error handler, if it > does not receive any error key for i18n it can generally report > and unexpected error? The page that James sent out has some useful info in it (which I am sure is not news to you). But it seems easy to set one big bad custom page for all runtime exceptions. And easy to override on a page by page basis.
Question about error keys. How are they generated? Is the error page created with a specific error key? Or is the message of an exception treated like an error key and a resource lookup performed to find the message for it? Or something else? > > Cheers > Andrea > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
