|
Can we really add this in 1.1? It seems like it should perhaps be considered a 2.0 issue.
I'm moving this off to 2.0 sine I don't think we could do a complete refactoring of this for 1.1
Do we really want to address this issue in Spring Batch? I think the FileUtils class encapsulates the non-batch specific complexity sufficiently. Unless there's a common usecase where such abstraction is badly needed I suggest we close this one.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BATCH-116added a FileUtils class that helps abstract out file handling. However, I still believe that this should probably be an abstract class that can be configurable in a common way. It might then make the entire package structure a little bit better as well, since the stax input source would extend AbstractFileInputSource.