Hi all, Andrea and myself recently had a discussion in jira that we think should probably take place on the wider list.
It has to do with CatalogListeners, and exceptions. The current behavior of the catalog is to protect itself against listeners that throw exceptions, and simply log the warning. Sometimes this behavior is intended, for those listeners that are "non-crucial". An example here would be the GWCListener. However for some listeners this behavior is uwanted and the exception should be thrown so that it can be reported to the user. Example here would be the GeoServerPersister. So we have a couple of options. It would be nice to hear what people prefer: 1) enforce catalog listeners to be well behaved, and do not catch exceptions thrown by listeners 2) come up with a special exception class CatalogException that when thrown by a listener will not be caught by the catalog. Thoughts? -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ 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
