Re: Jena-1427 - nextOptional()

I thought the upshot of the discussion was that we are okay with this because the Model API (the only place from which we support getting ExtendedIterators) will never have a null retrieved value and we clearly warn in the method documentation that the retrieved value must not be null. If the

Re: Jena-1427 - nextOptional()

I was expecting that with the discovery that optional throws a null pointer exception when the retrieved value is null would be enough to remove this functionality. I am concerned that once added it will be difficult to remove and that its operation is not congruent with stream based optional

Re: [VOTE] Apache Jena 3.6.0 RC1

+1 (binding) Builds successfully both from Git Tag and Source Release Tested on OS X Sierra Rob On 13/12/2017, 23:27, "Andy Seaborne" wrote: Hi, Here is a vote on a release of Jena 3.6.0. This is the first proposed candidate for a 3.5.0 release.

Re: Jena-1427 - nextOptional()

Claude, The JIRA ticket ends: [[ ASF GitHub Bot added a comment - 04/Dec/17 15:36 That was already the case in the PR and I've added text to call it out explicitly into the javadoc. githubbot ASF GitHub Bot added a comment - 04/Dec/17 15:40 Github user ajs6f commented on the issue:

Jena-1427 - nextOptional()

Perhaps i wasn't paying close enough attention but i didn't think adding optional and other streaming methods had been agreed. In fact i thought quite the oposite. If i am wrong please forgive the noise. If i am correct shouldn't 1427 be removed from the release candidate? Claude