I just brought my Spotlight up to date and had a lot of breakage in my
configuration file because of things like this...
//TODO use separate candidate map
candidateMapDirectory =
config.getProperty("org.dbpedia.spotlight.candidateMap.dir").trim();
if(!new File(candidateMapDirectory).isDirectory()) {
//throw new ConfigurationException("Cannot find candidate
map directory "+ candidateMapDirectory);
}
LOG.info("Read candidateMap.dir, but not used in this version.");
I get a null pointer exception because I don't define this property,
which must point to a real directory. The big joke is that this is "not
used in this version" so it's another nonworking artifact that gets
people confused when they start working with Spotlight.
Spotlight might benefit from dependency injection or another advanced
approach to configuration, but it would help a lot to wrap code like
the above in an existence check so I don't need to maintain a whole
bunch of bogus configuration parameters that the system doesn't use!
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
