[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596509#comment-14596509
]
Claude Warren commented on JENA-966:
------------------------------------
My other concern is the "distance" between 2.13 and 3.0 I understand there
will be refactoring of code involved in the move but to remove all iterators
and replace them with streams (even if there is a good technical answer for
Andy's objection) seems like a step (or several) too far. If I was to approach
migrating an application from 2.13 and I had to replace all iterators in my
code I think I would shy away. Furthermore, older code which will otherwise
compile under Java 8, will require deep reworking to make it function with Jean
3.0.
Is there a shim that will turn a Supplier into an Iterator? Are you proposing
we leave the entire installed base and extended code base behind at the 3.0
juncture?
Claude
> LazyIterator
> ------------
>
> Key: JENA-966
> URL: https://issues.apache.org/jira/browse/JENA-966
> Project: Apache Jena
> Issue Type: Bug
> Components: Core
> Affects Versions: Jena 3.0.0
> Reporter: Claude Warren
> Assignee: Claude Warren
>
> LazyIterator is an abstract class. The documentation indicates that the
> create() method needs to be overridden to create an instance. From this I
> would expect that
> now LazyIterator(){
> @Override
> public ExtendedIterator<Model> create() {
> ...
> }};
> Would work however LazyIterator does not override:
> remoteNext(), andThen(), toList(), and toSet().
> I believe these should be implemented in the class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
