Re: Markupstream.hasMore vs. MarkupStream.next

2016-05-15 Thread Thorsten Schöning
Guten Tag Thorsten Schöning, am Freitag, 13. Mai 2016 um 20:14 schrieben Sie: > Is this a bug or is using hasMore the wrong idiom in this case? https://issues.apache.org/jira/browse/WICKET-6165 Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am

Markupstream.hasMore vs. MarkupStream.next

2016-05-13 Thread Thorsten Schöning
Hi all, hasMore: return currentIndex < markup.size(); next:if (++currentIndex < markup.size()) {...} me: while (markupStream.hasMore()) {...} I get a null element within the while loop which I wouldn't expect to get. markup.size() is 73, currentIndex 72, so hasMore returns true, while ne