Probably due to a change in the algorithm for HashMap, or something similar.
This test expected a particular string in response, but Java 7 and Java 8 returned two different, but equivalent, strings.
Modify it so it will accept @prefix or xmlns: specifications in any order.
Replace PelletListener with a TBoxReasonerModule in the Application.
The reasoner will be accessible only through here, not as a context attribute or through the WebappDaoFactory.
Split out the initialization of the TBox reasoner from SimpleReasonerSetup.
Break out the filtering of TBox changes into a ConfiguredReasonerListener.
Refactor the threading logic into a BasicTBoxReasonerDriver.
Add a factory for creating VitroBackgroundThreads in an Executor.
Isolate the actual reasoner into a TBoxReasoner implementation. In this case, PelletTBoxReasoner.
Combine the consistency flag, error flag, explanation, and running status into one TBoxReasonerStatus object.
Replace PelletListener with BasicTBoxReasonerDriver, and associated classes.
Run the background thread from an ExecutorService.
Since nobody was using the FOREGROUND flag, and since its logic was flawed, skip it.
Make TBoxReasonerModule a module on the Application. Make the reasoner status available through the module.
Initialize it in startup_listeners.txt
Create a concrete class for PelletTBoxReasonerModule, and configure it in applicationSetup.n3
Get rid of PelletReasonerSetup.
Make it so the ExecutorService in BasicTBoxReasonerDriver uses a VitroBackgroundThread.,
Make TBoxReasonerModule a module on the Application. Make the reasoner status available through the module.
Initialize it in startup_listeners.txt
Create a concrete class for PelletTBoxReasonerModule, and configure it in applicationSetup.n3
Get rid of PelletReasonerSetup.
Make it so the ExecutorService in BasicTBoxReasonerDriver uses a VitroBackgroundThread.,
Merging list of populated properties with all possible properties,
we don't want to consider two properties equivalent just on the basis of base URI and label (domainPublic)
Why was this previously considered to be a good thing?
Use it to handle the odd behavior that a particular triple store might have.
In this case, the odd behavior is that TDB mangles XMLSchema#nonNegativeInteger to XMLSchema#integer in literal types.
the DataStructuresProviders must wrap their RDFServiceFactory in LoggingRDFServiceFactory,
and insure that their RDFService comes from that wrapped factory.
Create an interface for the Listener to act on.
If the changed object doesn't implement the interface, log a warning and do nothing, instead of throwing a ClassCastException.
The level values should never be null.
