[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600155#comment-14600155
]
Andy Seaborne commented on JENA-966:
------------------------------------
There is no strategy to move {{org.apache.jena.util.iterator.*}} to jena-base
from my point of view.
{{Iter}}, which is not tied into {{ExtendedIterator}} and is not just some
utilities for Iterators, is in jena-base and is used in severals modules.
My point of view is that the iterators in jena-core work perfectly well and can
be left alone now the functional idioms are in use. Changes for change sake
adds nothing for users and costs the project. Adding wrappers to put back
functionality taken out of working code seems rather odd.
> 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)
