|
Hi All,
I have a big problem with PagingIterator. This is a big show-stopper for me. I really appreciate in RC5 the new PagingIterator (I need to use scrollcursor since RC4) but your implementation has some problems.
First è in PagingIterator, when I use absolute or relative, you don't resync m_currentCursorPosition and hasNext() call releaseDbResources. It' not the good solution, releaseDbResources is in charge of developer (see correction attachment file).
Second è in PagingIterator, when you call next for the last record, the rsIterator call releaseDbResources and mark result to close. After this, if you call absolute or relative, you have this error java.util.NoSuchElementException: inner hasNext was false And you lose all benefits of scrollcursor.
Thanks Much, Thierry Legrain.
|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
