On Fri, 2002-10-11 at 13:24, Michiel Meeuwissen wrote: > > The behaviour of this propery is that it stops creating new nodes after > > if the count get above the limit specified inside the builder.xml > > (default will be 0 and means no limit) > I think we can take it for granted that you can of course put this property > in object.xml to speficy a 'general' value. Do we want to inherit this value to all it's subbuilders? (it would be nice..)
> > Personally i think that throwing an exception would be the best thing, > > since we have to notify the user that the query is 'invalid' > I'm not sure. Throwing exception will also destroy the valid results. > Generally I'm against exceptions while creating lists, because an error in > one entry (in this case the last onces), will fail the whole list. I would > support cutting the list and logging a big error (log.error, or even > log.fatal, the administrator should then contact the user...). But it is not > a big issue for me. I'll be +1 for any implementation of this. My reason for throwing an exception is that this way users get educated inside let's say the jsp-editors. Would it not throw an exception, people will always list object without any constrains. When it throws an exception, they have to get used to filling in a value every time... -- Eduard Witteveen Systeem Ontwikkelaar Publieke Omroep, Gateway C Kamer 101 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
