--- Will Glass-Husain <[EMAIL PROTECTED]> wrote: > Me, I'd just implement a custom logger that parses > the log text and detect > reference exceptions that way. It's not the most > elegant solution, but it > should work. >
OK, thanks, I think I'll go with the custom logger, although I agree it's kind of inelegant. Is there any reason behind the design decision of having some exceptions not passed all the way to the caller ? It does seem like these sort of errors are something that somebody should know about, and logging a message may not be the only thing anybody wants to do with them. > > On Thu, 2004-11-25 at 00:22, Matthew Keene wrote: > >> I'd like to be able to detect ReferenceExceptions > (and > >> other errors) that happen during a merge > operation. > >> At the moment they appear in the velocity.log, > but I'd > >> like to be able to display them to the user. Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
