+1, and I haven't purged any rights. In fact, I'm quite happy to make those rights permanent if you're interested in maintaining James with respect to Avalon on an ongoing basis.
On a loosely related note, we are facing a problem with Avalon's file repository due to a feature addition in the past year. The feature addition is that Avalon started numbering file repository instances, I believe the rationalization is that then you could have multiple file repositories co-exist in the same directory. The problem we're facing though is that if you add an account, and mail gets delivered to that account, then after you restart the server, the user mailboxes could get instantiated in a different order, and that account's mail would no longer be accessible. It's a pretty serious problem, and the only solution I've come up with is to take the Avalon code, repackage it as something in James, and remove the offending feature. How would you suggest we handle this? -- Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com Paul Hammant wrote: > Folks, > > Can I suggest that JAMES obsoletes use of ComponentManager and instead > uses its sucessor ServiceManager. > This is a really easy update, anyone could do it and it changes no > functionality of James, just brings it inline with other Cornerstone and > Avalon-apps blocks. > > I can voluteer to perform this maintenance type update, if it is voted > for and if you folks have not already purged my CVS rights... > > Regards, > > - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
