FWIW... I just grabbed the Jena source, imported it into my workspace and set my project to reference that, so I could debug into this as it's running. What I see is the code getting to line 864 in RDFDataMgr and executing this code:
parser = RiotReader.createParser(tokenizer, lang, base, output) ; which returns null. The next line tries to use the null reference, and hence the NPE. Looking at RiotReader.createParser(), I don't see anything in there that mentions JSON-LD at all. But the docs for java-jsonld say something like: "JenaJSONLD must be initialized so that the readers and writers are registered with Jena." and I do call the init() method. But I don't see how that registration process plays with this createParser() code. I'm guessing things have just gotten out of sync between Jena and the JSON-LD stuff? Phil This message optimized for indexing by NSA PRISM On Fri, Nov 15, 2013 at 12:01 AM, Phillip Rhodes <[email protected]> wrote: >> FWIW, I just tried again with Jena 2.11.0 and jsonld-java built from >> the latest Github sources as of yesterday, and I still get what >> appears to be the same exception. > > > Urgh, mis-spoke there... I meant to say "used jena-jsonld built from > the latest..." > > That said, I just switched it out to not use jena-jsonld and to use > java-jsonld directly (built from the latest sources), per the earlier > email, and it's still failing in the same place. This was also using > jena-2.11.0. > > > Phil
