Josh Spiegel

You could always define an unchecked exception but then it isn't clear to me how the close() would be communicated (e.g. on error, early exit, etc). Lambdas may be a...

I agree, we need to fix this to give a better error message. This makes it sound like there was something wrong with the input document.

Based on the bug descriptions, these issues do not appear to be duplicates. Can you give an explanation or reopen this issue?

Not only are they slow, but they will also likely cause a global lock when the ServiceLoader is invoked. I have seen people get burned by this in both JSON-P...

I had an additional thought - what would be useful is if here: https://github.com/javaee/jsonp/blob/master/api/src/main/java/javax/json/spi/JsonProvider.java#L90 There were an optional system property look up OVERRIDE_PROVIDER, or something like that, which statically loads...

@lukasj yes. And if possible, the Class.forName() on the value would happen outside of the method (static block) to avoid frequent class loading.

Parsers should already be able to skip allocating memory for events that are not consumed by the caller. I see no advantage to pushing query processing or redaction inside the...

No, there is also skipObject() and skipArray(). And there is no requirement that next() has to materialize anything. Materialization can be postponed until getXXX is actually called.

The ability to evaluate JsonPointer over JsonParser is reasonable but I don't think this should be added to the parser api. The parser api should remain independent of specific path...

This is my understanding as well. There is also JsonParser#skipObject() and skipArray() which can be used to avoid even having to manifest the skipped events.