On 13/09/12 21:28, Lebling, David (US SSA) wrote:
Andy,
While working on generating my own FileManager, I tried to print the
LocatorFile in the default FileManager (FileManager.get()). Its
Object.hashCode() implementation doesn't check for there not being an altDir,
which apparently is the case for the default instance. Result:
NullPointerException, LocatorFile.java, line 95.
Dave
-----Original Message-----
From: Andy Seaborne [mailto:[email protected]] On Behalf Of Andy
Seaborne
Sent: Monday, September 10, 2012 4:27 PM
3. A request, rather than a comment. During my debugging, one thing
Iwas seeing is a long, long pause while Jena goes out to the web after
unsuccessfully looking for a local ontology cached in the
OntDocumentManager (via loadImport). It would have helped during
debugging this if I knew how to set either the OntDocumentManager or
the FileManager to say "all my ontologies are cached in the
OntDocumentManager, so if you see yourself going out to the web, throw
an exception immediately, rather than even trying to connect." The
users of this software will be in an environment where every ontology
used is locally cached.
Is this from code? You can build your own FileManager and not include the URL
locator, then it will not go to the web (c.f. Fuseki protects local files by
creating a FileManger that does not access local files).
Andy
Fixed, thanks.
A quick note: this area is due for change - there is a new I/O framework
with (minor) changes to FileManger and friends [1]. Nothing
architectural but there may be a few noticeable changes.
e.g. TypeStream becomes TypedInputStream since we also want a
TypedOutputStream as well. Other than the name change, it won't affect
code (the current one does not work!).
Andy
[1] https://svn.apache.org/repos/asf/jena/Experimental/riot-reader/
