![]() Version 5.0.5 introduced the DiscardAwareFileListFilter implementations that have an interest in rejected files.įor this purpose, such a filter implementation should be supplied with a callback through addDiscardCallback(Consumer). ![]() The pattern filter might only pass the primary file (such as something.txt) but the “done” filter needs to see whether (for example) something.done is present. The CompositeFileListFilter approach is useful when a pattern filter is combined with a custom filter that looks for a secondary file to indicate that file transfer is complete. With the CompositeFileListFilter, since the AcceptOnceFileListFilter sees all the files on the first pass, it does not pass it later when the other filter does. ![]() (With the CompositeFileListFilter, all filters see all the files, but it passes only files that have passed all filters).Īn example of where the new behavior is required is a combination of LastModifiedFileListFilter and AcceptOnceFileListFilter, when we do not wish to accept the file until some amount of time has elapsed. ![]() Starting with version 4.3.7, a ChainFileListFilter (an extension of CompositeFileListFilter) has been introduced to allow scenarios when subsequent filters should only see the result of the previous filter. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |