Justin Deoliveira ha scritto: > <snip> >>> >>> 1) enforce catalog listeners to be well behaved, and do not catch >>> exceptions thrown by listeners >> >> This is the cleanest approach imho, you always get to know when things >> go south. Downside, it might break operation, the current approach >> allows some sort of graceful degradation (thought in some cases it's >> not so graceful, restart GeoServer and your config is gone ;-) ) > > It goes both ways. Say you have a misbehaved listener that executes > before the configuration persister. The same thing will happen (the > persister will not execute so after restart you lose data).
Good point! Hmmm... I guess I'm starting to like option 2 better ;-) Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
