ensure that xml record reader is closed
return null instead of an object to indicate that no batch result is available
if total records count cannot be calculated in advance, do not log 0 but "N/A" instead which is more adequate
improve RecordReader API design : make readNextRecord and close methods throw an Exception to be handled by Easy Batch engine
fix issue#14 : Easy Batch crashes if an unexpected exception occurs during opening/closing data source reader
fix issue#15 : Easy Batch crashes if an unexpected exception occurs during reading the next data source record
Improve JdbcRecordReader implementation : when an SqlException occurs, do not throw a RuntimeException (that cannot be handled correctly by the engine). Instead, log an error message and return an appropriate result.
Improve XmlRecordReader implementation : when an XMLStreamException occurs, do not throw a RuntimeException (that cannot be handled correctly by the engine). Instead, log an error message and return an appropriate result.
fix issue#16 : Easy Batch crashes if an unexpected exception occurs during data validation