Perhaps consideration should be give to wrapping mailets in mailets, that way the tracking mailet could contain any mailet, all it has to do is delegate calls to the mailet methods to the wrapped class, and intercept those its interested in on the way.
I suspect the config model isn't up to this though. I'm also concerned that this mailet is not portable, as it relies on the component mamanger and a new James service, but thats beside the point unless we isolate mailets from the Comonent manager. d. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 28 February 2003 15:30 > To: James Developers List > Subject: RE: User-Log > > > > If he wants to change GenericMailet for his own purposes, > > that's fine. Otherwise, he might want to create a > > GenericTrackingMailet for those mailets that will use his > > tracking service. > > > > --- Noel > > That was going to be my next question - I was not sure as to > how much we want to actively support variations of James, > and the creation of a new base class makes a whole lot of > sense. > > > > _______________________ > thanks, > alan > > --------------------------------------------------------------------- > 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]
