TCK failure, NPE in JsonProvider.createParser(InputStream)

[starksm64]

The TCK jsonprovidertests have a test that verifies calling jakarta.json.Json.createParser(InputStream = null) throws a JsonException. Currently this is seeing an NPE as described in this issue:
jakartaee/platform-tck#1002

Current parsson version in glassfish is 1.1.0.

[starksm64]

It looks like the root cause of this is not loading the com.sun.ts.tests.jsonp.provider.MyJsonProvider class:
jakartaee/platform-tck#1003

[jbescos]

I think there is currently no deterministic way to know which implementation will be loaded first from the META-INF/services. When 2 different implementations exists in the classpath there is no logic to determine which one should be used.

We should agree in a common solution, because I think this is also a problem in mail and jsonb at least.

@lukasj what is your opinion in this?.

[jbescos]

I discussed with @lukasj and he told me there is already one bundle dependency that contains Parsson implementation and JSONP API. This bundle does not have META-INF/services, so it will allow other implementations in the classpath to be loaded.

In few words, you need to remove from GF any Parsson and JSONP dependency, and add this one instead org.eclipse.parsson:jakarta.json:
https://github.com/eclipse-ee4j/parsson/blob/master/bundles/jakarta.json/pom.xml