> > As far as backwards compatibility is concerned, this is partially > blown > > already with the enabled flag required in config files so existing > > config files will no longer work. Admittedly this is much easier to > > fix. > > There is a huge difference here. Basically we can (and should) write > some simple XML transform code to change the config file as necessary. > Even if we don't do this, any administrator can be instructed to do > minor adjustments to their config file.
+1 for James configuration to change between versions is a completely different matter to breaking a published API without warning. Besides we can control our own code, and back out changes we don't like, but we're at the mercy of Avalon for an awful lot of James. I've been toying with a Mailet API which could be completely free of Avalon dependance, even in mailets that require repository access,perhaps this is the way to procede? d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
