On 06-07-2005 13:51, "Adam R. B. Jack" <[EMAIL PROTECTED]> wrote: >> Oh, and you're now greeted with 100s of lines of error messages if you >> don't have a db connection or a messed up database :-). > > Like this? ;-) > > http://vmgump.apache.org/gump/gump3/run.log
Fancy! > BTW: Can we fix the schema, or do we need to re-instantiate it? The latter. I'll try and take care of it tonight. >> Adam, perhaps you could take a pass through the code and point your >> finger at stuff that's messed up or which doesn't make sense? Also, one >> todo that'd be nice to have when building dynagump is to actually have >> long logs stored in the DB. I know you've spent a lot of time on the >> builder plugins. For some reason no build_log properties are being set. >> Could you try and get that running? > > Sure. > > In return, could you look into the problem above seeking to understand why > these failures cause Gump to fall off IRC, not exit? Huh? Ehm, will do. > Are certain plugins not > getting called when another fails? I'm never quite sure how Gump3 copes with > errors. Its supposed to be pretty simple: all exceptions that occur inside a plugin bubble up to the algorithm that's being run. The idea is that you configure the ErrorHandler used with the Algorithm. Using the OptimisticLoggingErrorHandler swallows the exceptions that plugins raise, whereas the LoggingErrorHandler re-raises all of them. Maybe the post-processing plugins are configured with the LoggingErrorHandler or something. I'll check. Cheers, LSD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
