I suppose you could write a Property setter rule to do this. The general theory behind Digester is not for validation, but configuration. It will try and match as many properties from the XML to the actual bean as it can, but it was actually designed to not care if it can't.
Hope this helps. Scott Sanders > -----Original Message----- > From: Greg McCreath [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 18, 2002 4:05 AM > To: '[EMAIL PROTECTED]' > Subject: Digester/BuanUtils Error trapping ... > > > > Hi All, > > This is my first posting here. I'm looking at using the > Digester class to construct object trees from a config XML > file. I looks like a handy tool. I've been investigating it > this morning and noticed that no error/exception is thrown by > beanutils when a property setter does not exist for a class > defined in the config XML. The code just performs a > 'continue' and ignores what might be a nasty cause of > problems. I can't trap it in DTD for every possible class as > it is arbitrary. > > It seems as though I have no way to detect if logical errors > exist in the XML. Also, I've noticed a SAXException is > thrown when an invalid class in contained in the XML (?). > > Am I wrong? Can I detect when property setters do not exist? > > Many thanks > > Greg. > > -- > To unsubscribe, e-mail: > <mailto:commons-dev-> [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]>
