Use of JSON-LD module in RDF4J 5.0: JsonProvider implementation on classpath via SPI

[hmottestad]

Discussed in #5039

^{Originally posted by aschwarte10 June 20, 2024}
Hi,

we are currently doing more extensive tests of RDF4J 5.0 and have a question to the JSON-LD module, specifically rdf4j-rio-jsonld.

When using this, it requires the following dependencies:

• no.hasmac:hasmac-json-ld
• jakarta.json:jakarta.json-api
• org.glassfish:jakarta.json

With this classpath it looks like there is no implementation of JsonProvider automatically detected, e.g. via SPI. It looks like the implementation falls back to the implementation of org.eclipse.parsson:parsson (which at least on the json-ld module is not on the RDF4J classpath).

We found that the glassfish binary provides an implementation, which is not registerd using SPI though.

How is this meant to work generally in RDF4J?

Note: in our case we simply registered the implementation of JsonProvider from glassfish manually using SPI on our classpath.

[jetztgradnet]

This change has some unintended consequences now with Glassfish JSON no longer being the default implementation, but rather Eclipse Parrson. See #5233 for details.
The original cause for this issue could be that one needs to rather refer to the dependency with the module qualifier, as outlined in jakartaee/jsonp-api#260 and the linked readme (now only available in an older branch).