Yes, I'm not happy with that change just yet. This requires a change to the mailet API, which is something I want to discuss much more before changing. We have this issue to change when we do make a new version of the mailet API. -- Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com
Noel J. Bergman wrote: > Andrei, > > I'll be happy to do the code, but does anyone else want it, and are people > OK with a MailetContext.getMailetLogger() method? I'd just as soon not > submit a change that gets bitbucketed. > > --- Noel > > -----Original Message----- > From: Andrei A. Ivanov [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 07, 2002 9:25 > To: James Developers List > Subject: Re: Finer Logging Control for Mailets/Matchers > > Hi, > > >>We could expose >>MailetContext.getMailetLogger() > > > Let's do it, the sooner the better. > > What about other ideas: like make it possible to specify per mailet logger > etc? > > Andrei > > ----- Original Message ----- > From: "Noel J. Bergman" <[EMAIL PROTECTED]> > To: "James Developers List" <[EMAIL PROTECTED]> > Sent: Friday, June 07, 2002 4:04 PM > Subject: Finer Logging Control for Mailets/Matchers > > >>Andrei, >> >>James implements MailetContext. MailetContext provides the two log > > methods > >>available to Mailets. Those two methods use: >> >> getMailetLogger().info(...); >> >>which is a private method of James. We could expose >>MailetContext.getMailetLogger() for matchers and mailets that want finer >>control over the log level. >> >>--- Noel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
