Thanks for the quick response. I suspect the TTL for N-TRIPLE was a typo. I will delve into it again this evening but I think we can assume that the issue is closed.
-- Claude On Thu, Apr 4, 2013 at 1:19 PM, Andy Seaborne <[email protected]> wrote: > (from memory) The TestReaderEvent tests that read start and read end >> markers are recorded in the listeners. The RIOT reader is not doing this. >> > > You're right - except for RDF/XML (where the intergration is inverted, > RIOt wrappers an old style Jena reader) it is not sending events. Now, > "was" - fixed. > > Your test case passes for me now. > > > I suppose I should build a test for the reader implementations that will >> test this functionality. >> > > > Attached is a minimal test case example. > >> >> The archive contains a java test as well as a pom.xml >> >> If the ARQ is included in the POM the tests fail, if the ARQ is not in >> the POM the tests pass. >> > > In your original message you said that you were getting the TTL reader for > NT. Was that just a typo? and now > > > ModelCom.getReader("N-TRIPLE") > RDFReaderFImpl.getReader("N-**TRIPLE") > String className = langToClassName.getProperty(**lang) returns > "com.hp.hpl.jena.n3.**N3JenaWriter.**JenaReadersWriters$** > RDFReaderRIOT_TTL" > > been sorted out? > > A) The class name is wrong > B) It's not an N-Triples syntax reader. > > Andy > > >> -- Claude >> > > -- I like: Like Like - The likeliest place on the web<http://like-like.xenei.com> Identity: https://www.identify.nu/[email protected] LinkedIn: http://www.linkedin.com/in/claudewarren
