Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0.4
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      I have no need of a skip limit and yet Spring Batch forces me to impose an artificial one. I can set that limit suitably sky high, but this is not an accurate representation of my client's business requirements.

      My ideal solution would be for the skip limit to not be required in xml and for Spring Batch to assume that unless ALL records are skipped that the batch job succeeded.

        Activity

        No workflow transitions have been executed yet.

          People

          • Assignee:
            david_syer Dave Syer
            Reporter:
            caoilte Caoilte O'Connor
          • Votes:
            10 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

            • Created:
              Updated: