> That's where things start to suck. > But is this really a Mailet API issue - or just lots of fuss over the > current mailet container implementation?
Its both, the current API doesn't provide enough access to the services we get from avalon in an independant way, say by wrapping them in an interface, and the lack of seperation by the container means that mailets can be developed which directly access avalon provided services. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
