BeanReflectionException? Sent from tablet device. Please excuse typos and brevity. On Jun 18, 2012 4:30 AM, "Simone Tripodi" <simonetrip...@apache.org> wrote:
> Guten morgen, Bene, > > > My personal favorite is ReflectionException. I don't think, that we > > should prefix classes wie BeanUtils*, because this information is > > contained in the fully qualified class name. > > +1 I wouldn't happy at all to add a BeanUtilsException, > ReflectionException sounds the good candidate for me as well, with > following potential hierarchy: > > ReflectionException > - PropertyNotFoundException > - ReaderMethodNotFoundException > - WriterMethodNotFoundException > - ... > > > The problem is, that > > there is already a ReflectionException in javax [2]. So I guess we can > > not use that name? > > I don't see where the issue could be, since full qualified names would > be different: > > javax.management.ReflectionException != > org.apache.commons.beanutils2.ReflectionException > > there are no chances for a naming conflict. > > A suggestion: > > we are often using the String.format() method to format Exception > messages - which is very good, IMHO - and since we are introducing a > new Exception we can take advantage for reducing its use, centralizing > the message format in the new exception itself, have a look at the > Digester's ErrorMessage <http://s.apache.org/wiR> > > Alles gute und dankeshön, > -Simo > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
