Description
The code looks like
catch (NetarkivetException e) { // Our exceptions don't stop us success = false; // With our exceptions, we assume that just the // processing of this record got stopped, and we can // easily find the next handleOurException(e, arcFile, arcFileIndex); } catch (Exception e) { success = false; // Strange exceptions do stop us handleException(e, arcFile, arcFileIndex); // With strange exceptions, we don't know // if we've skipped records break; }
But why do we set success=false when handling NetarkivetExceptions? This contradicts the comments and results in the batch job being marked as failed even though we claim to be able to handle this case.