Rio JSONLD module should not register GlassFish JsonProviderImpl

[jetztgradnet]

Current Behavior

the rdf4j-rio-jsonld module registers org.glassfish.json.JsonProviderImpl in its META-INF/services/jakarta.json.spi.JsonProvider (see source file).

As this module does not actually provide that implementation, this is bad and unexpected behavior, especially as GlassFish JsonProviderImpl is the legacy implementation and has been superseded by Eclipse Parrson, which has a different classname org.eclipse.parsson.JsonProviderImpl (see Parrson's version of META-INF/services/jakarta.json.spi.JsonProvider).

As a result, I need to continue using the obsolete dependency of implementation org.glassfish:jakarta.json:2.0.1 as only that actually provides the implementation class org.glassfish.json.JsonProviderImpl.

As a consequence, I get exceptions which are caused by this:

Caused by: java.util.ServiceConfigurationError: jakarta.json.spi.JsonProvider: Provider org.glassfish.json.JsonProviderImpl not found

Please note that the jsonld-legacy module does not expose the same behavior, there is no registration for META-INF/services/jakarta.json.spi.JsonProvider.

Apparently this behavior was added as part of GH-5041.

Expected Behavior

RIO JSONLD should not pre-register any JSON provider, leaving me free to choose any implementation.

Steps To Reproduce

No response

Version

5.1.0

Are you interested in contributing a solution yourself?

None

Anything else?

No response