On 4/25/06, Jimmy, Jing Lv <[EMAIL PROTECTED]> wrote: <SNIP> > For the example 1) I mean the spec usually merge several exceptions into > one parent exception. In this situation, commonly RI throws child > exception itself, although it is hard to tell what RI exactly throw in > some special situation. > And I think we are not "improving" the spec if we throw child > exceptions, it is just convention or something writing "throws > IOException" instead of writing "throws connectionException, > UnknownHostException". We do follow spec if we throw child exception. > > > The idea behind the question is: why not just copy RI in this case > > (conforming Tim's guidelines)? > > > > Yes,I firmly agree with Tim's guidelines. We should first follow spec > and then RI. In this case, we still follow the spec, right? :)
Absolutely! The question was: why we decided to throw sub-classing exceptions. If the answer is: "because RI does" I completely support such decision (which completely complies Tim's guidelines). -- Anton Avtamonov, Intel Middleware Products Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
