[
https://issues.jboss.org/browse/ISPN-4375?page=com.atlassian.jira.plugin....
]
Paul Ferraro updated ISPN-4375:
-------------------------------
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? (was: Currently,
EntryIterable.close() throws an exception, which is inconsistent with the runtime
exception conventions in the rest of the infinispan api.)
EntryIterable need not throw an exception on close()
----------------------------------------------------
Key: ISPN-4375
URL:
https://issues.jboss.org/browse/ISPN-4375
Project: Infinispan
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Core
Affects Versions: 7.0.0.Alpha4
Reporter: Paul Ferraro
Assignee: Paul Ferraro
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?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)