Bug 4303

Summary: Break RetryListener down into multiple interfaces?
Product: jbatch Reporter: chrisschaefer
Component: sourceAssignee: cvignola
Status: CLOSED FIXED    
Severity: enhancement CC: issues
Priority: P5    
Version: 1   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS   

Description chrisschaefer 2012-11-12 17:53:47 UTC
Rather than having one interface for Read, Write and Process - RetryListener should be broken down into specific interfaces such as RetryReadListener, RetryProcessListener, RetryWriterListener. Seems like a lot to possibly have to no-op or use annotations as a work around.
Comment 1 cvignola 2012-11-19 12:49:07 UTC
This is a reasonable argument.  The original intent was to match Spring Batch interfaces where it made sense.  This one does in terms of its singularity, but the methods are different.  I will socialize multiple interfaces with the expert group and see where we end up.
Comment 2 cvignola 2012-12-06 17:34:49 UTC
Yep, you're right.  We should have an interface for read, process, write.  That's what we'll do.