diff does seem to fix the bug in a new instance but it is not backward compatible. Serge is doing work that handles both changing IDs and backward compatibility without breaking any other users of Avalon File Repository.
I had looked at this part of code in some detail almost 1.5 years back. Wanted to reuse this for NNTP Repository, but the performance was terrible. I suspect that performance of file repositories may not be that good, but then again a lot has changed since then. The interaction between RepositoryManager/AbstractFileRepository in Avalon is bug prone. Avalon committers on this list may want to review it. At least one problem is that the contents of persistent repository are filtered based on expected file extension and the extension calculation is not persistent. Harmeet ----- Original Message ----- From: Danny Angus <[EMAIL PROTECTED]> Sent: Dec 21, 9:58 AM > Does this really fix it completely, or just the trivial case? > > I thought that if you change your config the repositories can end up with > different ID's, such that existing repositories will no longer recognise old > files as their's
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
