james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <Paul_Hamm...@yahoo.com>
Subject Re: Serviceable to Composable changeover
Date Mon, 03 Jun 2002 13:04:06 GMT
Danny,

>>Err, actually I am advocating closer binding with Avalon-Framework
>>interfaces.
>>    
>>
>
>I'd rather see the mailet API developed completely independant of any
>dependancies at all, apart from Java Mail.
>It would then be up to James' implementation to conform to avalon design
>imperatives, and benefit accordingly.
>  
>
Yes, a maillet may impl all, any or none of the Avalon-Framework 
methods.  James (the container) recognises that is it instantiates 
maillets and decorates them accorting to lifecycle concepts.  What I'm 
anxious for you folks to avoid is the duplication of things illustrated 
by Avalon-Framework.

>I'd like to see mailet being used by people and products with no connection
>to James at all, and no reason for them to even know about James.
>  
>
Multiple implementation of maillet aware container.  Agree.

- Paul


--
To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>


Mime
View raw message