[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599637#comment-14599637
]
A. Soroka commented on JENA-966:
--------------------------------
[~andy.seaborne], I am still not clear about your objection to deprecating
{{Map1Iterator}} in favor of {{Iter::map}}. Are you entirely against this or is
there something I can do to make it more attractive? My hope is to find those
places where an {{ExtendedIterator}} is not in fact needed and replace them
with a simple use of {{Iter::map}} and for the rest, use {{WrappedIterator}}
around a call to {{Iter::map}}. There would be no direct connection from
{{Iter}} to the classes in {{<jena-core>/org.apache.jena.util.iterator}},
although there would be a connection the other way. I thought the larger
strategy was indeed to shift from {{<jena-core>/org.apache.jena.util}} to
Atlas, in {{<jena-base>}}?
> 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)
