Getting null when using RIOT.getContext() about jena HOT 5 CLOSED

It will work outside Netbean using Maven:
mvn exec:java -Dexec.mainClass="com.myworks.testprog"

but still returns null using the "java -jar" method.

from jena.

After some digging, I added:
ARQ.init();

and now the expected results print. I never had to do this before. I suppose something is different in this new JDK I am using.

from jena.

This could be because the combined jar does not include the service loader files:

https://jena.apache.org/documentation/notes/jena-repack.html

For each of the jena jars included, the repacking needs to include (concatenate into one file) the contents of all
META-INF/services/org.apache.jena.sys.JenaSubsystemLifecycle files in one file in the combined jar.

These are what drives Jena initialization using Java ServiceLoader. The JenaSubsystemLifecycle in Jena calls ARQ.init amongst other things.

from jena.

That did the trick. I was able to remove the ARQ.init() line after that. The weird is that I've used a shaded jar in this project for years with Jena without needing this change, so I'm not sure what changed, but it's an easy enough change. Thanks Andy!

from jena.

There was probably partial initialization - normally initialization happens when Jena is first touched by app code. An app can force it with JenaSystem.init(). There is still class initialization happening and ARQ.init can be triggered (or "was triggered") by other routes.

https://jena.apache.org/documentation/notes/system-initialization.html

including how to debug.

from jena.