+1 to James for both topics, let's start from a basic exception - naming proposals are welcome.
I'll create the wiki page later after dinner - that WE is too much sunny to stay at home ;) best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Jun 15, 2012 at 5:48 PM, James Carman <[email protected]> wrote: > It shouldn't. If you're catching the superclass (for instance > BeanUtilsReflectionException) and later we start to throw > BeanUtilsInstantiationException which extends > BeanUtilsReflectionException, I don't think you'll run into problems. > > On Fri, Jun 15, 2012 at 10:26 AM, Benedikt Ritter > <[email protected]> wrote: >> 2012/6/15 James Carman <[email protected]>: >>> On Fri, Jun 15, 2012 at 9:39 AM, Benedikt Ritter >>> <[email protected]> wrote: >>>> - Wrapper Exceptions: I thing we should discuss, how a exception >>>> hierarchy could look like. I'll make a suggestion ASAP. >>>> >>> >>> I don't want to duplicate the hierarchy. I would say start with a >>> generic exception type for now. If folks ask for more specific >>> subtypes later, we can add them. >>> >> >> Would adding more specific RuntimeExceptions later break bc? I think >> no, because RuntimeExceptions don't have to be part of the method >> signature. But I'm not sure :-) >> >> thanks, >> Benedikt >> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
