commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <ja...@carmanconsulting.com>
Subject Re: [BeanUtils2] Thoughts about the API
Date Fri, 15 Jun 2012 15:48:28 GMT
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
<beneritter@googlemail.com> wrote:
> 2012/6/15 James Carman <james@carmanconsulting.com>:
>> On Fri, Jun 15, 2012 at 9:39 AM, Benedikt Ritter
>> <beneritter@googlemail.com> 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: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message