If you look at the implementation CatalogImpl IllegalARgumentExceptions are thrown when a problem occurs adding a store / resource / namespace / workspace / etc... We should probably add a throws declaration to the interface.
If you think a checked exception would be better we can go that route as well. Andrea Aime wrote: > Hi, > I was looking into the Catalog API and only > now I noticed there is no exception throwing > whatsoever. So all issues are going to be > reported by runtime exceptions? > What should be the pattern to save a new > resource? > > Cheers > Andrea > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > !DSPAM:4007,48651b48196581431913854! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
