Serge,
> +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?
Well if there is a fix, then we could put it back in Cornerstone CVS.
How about this - extra config for that block ......
<mailstore>
<repositories>
<repository
class="org.apache.james.mailrepository.AvalonMailRepository"
naming="numbered">
..
</repository>
<repository
class="org.apache.james.mailrepository.AvalonMailRepository"
naming="some thing else">
..
</repository>
</repositories>
</mailstore>
This means there is one codebase that can be used for James and other
Store using blocks.
- Paul
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
