[esb-issues] [JBoss JIRA] Updated: (JBESB-2178) Add ability to reflectively inject FileFilter into file-based gateways

Add ability to reflectively inject FileFilter into file-based gateways ---------------------------------------------------------------------- Key: JBESB-2178 URL: https://jira.jboss.org/jira/browse/JBESB-2178 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Ryan Hochstetler Fix For: 4.5 It would greatly enhance the flexibility of the file-based gateways if one could specify a class implementing java.io.FileFilter as part of the configuration of that gateway. This would be a far more flexible manner of choosing which files to accept than the clunky extension-based mechanism currently in place. Please consider the following use case: One unified drop-box: uncompressed files of various extensions are picked up for "Service A" (.dat, .txt, .etc), and compressed files of various extensions are picked up for "Service B" (.zip, .tar.gz, .rar). Currently, this would require six different file channels, whereas my suggestion would only require two. Sure, I could split the drop boxes into "compressed" and "uncompressed", but with the "no input-suffix required" feature broken, I'd still need six. Another use case might be that we wish to accept only files which are of a certain age onto the bus. Another might filter on file size. (I actually wrote a FileSizeLimitComposer(long threshold) extends LocalFileMessageComposer to accomplish this task by setting bytes as the payload at or below the threshold and a lightweight file handle (string or java.io.File) as the payload above the threshold, but a FileFilter would have been a much better option). My point being: JBESB is already internally using java.io.FileFilter (FileGatewayListener._inputFileFilter), why not make the FileGatewayListener extremely flexible by allowing us to define our own FileFilters?