How far should we go you ask, Just that far. ;-) It does not need to be an all-or-nothing approach.
Tal > -----Original Message----- > From: craigmcc@localhost [mailto:craigmcc@localhost]On Behalf Of Craig > R. McClanahan > Sent: Tuesday, November 13, 2001 11:30 AM > To: Jakarta Commons Developers List > Subject: Re: [Digester] - appreciation and suggestions > > > > > On Tue, 13 Nov 2001, Tal Dayan wrote: > > > Date: Tue, 13 Nov 2001 11:09:54 -0800 > > From: Tal Dayan <[EMAIL PROTECTED]> > > Reply-To: Jakarta Commons Developers List > <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: [Digester] - appreciation and suggestions > > > > Hello, > > > > In the last day or so we evaluated Digester and we just decided > go with it > > and convert all of our configuration files from our proprietary > format to > > XML/Digester. > > Digester is a real time saver and we appreciate it. > > > > Here is a small suggestions: > > > > When specifying rules, such as addObjectCreate, it would be > nice to have a > > method that accepts > > a Class object and takes its name internally. This may save > spelling errors > > and is a little bit more type safe. > > > > This can certainly be done, but how far do you go? There's a bunch of > stuff that you cannot check until runtime anyway, because you don't know > ahead of time what is going to be on the object stack. The only safe > way to use libraries as flexible as this is *rigorous* unit testing :-). > > > Thanks, > > > > Tal > > > > Craig > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
