Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-4375

EntryIterable need not throw an exception on close()

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.0.0.Alpha4
    • Fix Version/s: 7.0.0.Alpha5
    • Component/s: Core
    • Labels:
      None

      Description

      Currently, EntryIterable.close() throws an exception, which is inconsistent with the runtime exception conventions in the rest of the infinispan api. In fact, none of the methods called from within the implemention's close() method throws a checked exception, so why should the close() method on the interface?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                pferraro Paul Ferraro
                Reporter:
                pferraro Paul Ferraro
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: