> 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.
Very clever and general solution! Nicely done. :-D Best of the lot so
far.
> I suspect the config model isn't up to this though.
<mailet match="..." class="Wrapper">
<Wrapper-target>RealMailet</Wrapper-target>
<Wrapper-param>...</Wrapper-param>
<foo>...</foo>
</mailet>
The wrapper would instantiate the inner mailet instance, and pass along the
lifecycle calls, including the config object. The inner mailet wouldn't
know about or bother with the wrapper's configuration parameters.
> I'm also concerned that this mailet is not portable
I don't think that there is much question of that, right now. But at least
it is isolated into one place.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
