The JndiRepositoryFactory now uses the "type" value (as specified in the 'conf/context.xml' for Tomcat) as the major impetus for registering the ModeShape JcrEngine instance or a javax.jcr.Repository instance. If an engine is to be registered, then the existence of a 'repositoryName' is logged as a warning. If a repository is to be registered, then the 'repositoryName' value is expected and must match an existing repository; all other cases are logged as an error.

The JndiRepositoryFactory now uses the "type" value (as specified in the 'conf/context.xml' for Tomcat) as the major impetus for registering the ModeShape JcrEngine instance or a javax.jcr.Repository instance. If an engine is to be registered, then the existence of a 'repositoryName' is logged as a warning. If a repository is to be registered, then the 'repositoryName' value is expected and must match an existing repository; all other cases are logged as an error.

The MS Office sequencer is using a different value of Apache POI than is being inherited from the Tika library used in the Tika Text Extractor module. This change upgrade the sequencer to also use 3.7, adds several unit and integration tests, and also makes a number of fixes to the way the sequencer works.

The MS Office sequencer is using a different value of Apache POI than is being inherited from the Tika library used in the Tika Text Extractor module. This change upgrade the sequencer to also use 3.7, adds several unit and integration tests, and also makes a number of fixes to the way the sequencer works.

MODE-1245 because of the performance of the jpa source (i.e., mysql, oracle, etc.), it could cause a timing issue with loading the cache and finding the node. Therefore, by moving the find to the end of the method and, on the rare case the find isn't found on the first lookup, a loop of maximum 5 tries will be peformed in order to allow the cache time to fill.

MODE-1245 because of the performance of the jpa source (i.e., mysql, oracle, etc.), it could cause a timing issue with loading the cache and finding the node. Therefore, by moving the find to the end of the method and, on the rare case the find isn't found on the first lookup, a loop of maximum 5 tries will be peformed in order to allow the cache time to fill.