On Mon, May 5, 2008 at 5:54 PM, Hasan Muhammad <[EMAIL PROTECTED]> wrote:
> So if plugins want to create their own monitor, what will happen in this > case? Now, the way plugins have control is, by looking at the messageID of > the problem, they can decide whether they want to change the behaviour > from > a warning to error, etc. > > regard > Hasan > > On Fri, May 2, 2008 at 11:23 AM, Jean-Sebastien Delfino < > [EMAIL PROTECTED]> wrote: > > > Simon Laws wrote: > > > > > > > > Depending where you actually catch the exception you should be able to > > > continue on and process the next artifact. > > > > > > > > Hmmm, the idea with monitors is to allow the processing code to report > > warnings and continue or multiple errors per artifact for example. > > > > Not sure about how it'll work with exceptions? > > -- > > Jean-Sebastien > > > The suggestion is still that monitors get access to all the errors/warnings that the system generates for display to the user so you will be able to take the same approach. Simon
