If you need to do this with the current version of James you can create a new SenderLog Component (at the Avalon level). The SenderLog Component can be have it's own configuration category name and logging level. Then your mailet could simply lookup the SenderLog Component at runtime and use this to do the actual logging.
It's kind of messy to add a new Component because you need to change james.xinfo as well as the assembly configuration file and rebuild James, but it's definitely doable. Steve > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 30, 2003 9:58 AM > To: James Users List > Subject: RE: User-Log > > > > In fact, I don't understand the process that matches > maillet name and > > declaration in the XML file James-server > > James uses Avalon logging. Mailets, however, do not have > fine grained logging support in James v2. Better logging is > proposed for James v3, with a revision of the Mailet API. > > There are things that you could do to work around it, if > necessary. Basically, roll your own logging, or make some > changes to access the underlying Avalon infrastructure. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
