On 11/10/06, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Talking about simple backward compatible, mailet api compatible (james
specific) enhancement, have you any proposal/preference?
Just off the top of the head idea..
One posibility would be that you could create properties which could
be accessed via a static, it would be a James only "feature"
Properties JamesMatcherProps.getExtendedProperties.(Matcher matcher);
...
James would wrap matchers and the wrapper would include get and set
extendedProperties
set them when you instatiate and configure the matcher.
...
JamesMatcherProps.getExtendedProperties(Matcher matcher){
if(matcher instanceof MatcherWrapper){
return ((MatcherWrapper) matcher).getExtendedProperties();
}
}
About what you write in the following text, they all are good ideas, but
I think that we should probably better start evaluating the integration
of third party workflow/rule engines: they could give us also tools to
manage the complex configuration.
That IMHO should be an implementation detail, the API should only be
allowing you to do it, not forcing it.
d.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
