- unnecessary dependencies to slf4j have been removed - the LogFactory from common searches for SFL4j's API in the classpath prior to defaulting to java.util
… dummy cache store (which is in fact, an in-memory cache store). Reason for the change was that the tests take double the time to run if the FileSystemCacheStore is used and there isn't any reason (test-wise for the RemoteISPNSource) to really use that.
The anonymous authentication provider is now being initialized after the chain of custom authentication providers (rather than before). Also, the anonymous provider is no longer being initialized when the anonymous roles is set to an empty string. All unit and integration tests pass with these changes.
Certain JCR-SQL2 full-text search criteria were not being processed correctly. Any f.t.s. criteria that specified a single property resulted in an incorrect query plan. Several changes were made to correct this behavior, and new unit tests were added.
The REST client library was versioning only the 'jcr:content' child node of an 'nt:file' node. While that's acceptable (since it's where the file's content is actually stored), it's better if the 'nt:file' node itself was versioned. This change simply changes the node where the 'mix:versionable' mixin is applied. When a new 'nt:file' node is uploaded, that node is now made versionable instead of the 'jcr:content' child. All existing content is still handled and versioned correctly (as it was), and this change only affects content added using a RESTful client that contains the fix. This change only affects the RESTful client, which is never used within the server-side installation of ModeShape. All unit and integration tests pass with these changes.
In certain cases, XMI models might contain references to the annotated objects not as XML attributes but as child elements. (This bifurcated design is considered a benefit to XMI, though not sure why.) Anyway, the problem appears to be that a virtual model contains an (empty) "annoation" for the physical model. It's not clear to me why the Designer would produce such an annotation. Additional tests were added to reproduce the problem with the original models and VDB. After the fix, the tests pass as expected. All unit and integration tests pass with these changes.
Moved the URL an REPOSITORY_NAME constants from the JcrRepositoryFactory implementation class into the existing org.modeshape.jcr.api.RepositoryFactory interface. These constants can be used when programmatically defining the parameters to pass to the RepositoryFactory.getRepository(Map) method. Also added more JavaDoc, and deprecated the constants in the JcrRepositoryFactory class. All unit and integration tests pass with these changes.
…connectors ISPN 5 uses a newer version of jboss-logging, therefore when this connector is used, some transitive dependencies need to be disabled
…uest is always frozen
…te hangs when repository starts up. Also, added a test case which reproduces the steps in MODE-1235
Without this, the Java Sequencer and the JBoss AS assembly would bring in 2 different versions, causing the Ant script from JBossAS to fail when unsigning the jar.
…s in a disk store
…ted issues may be easily verified
The examples in the RESTful Service chapter did not show including the "Content-Type" HTTP header. The service will correctly return JSON if this header or "Content-Type" header is supplied in the request. However, an error will result if a different content-Type header is provided. This change only affects the Reference Guide.
Corrected several behaviors of what is allowed and not allowed for modifying nodes that are checked in, per Section 15.2.2 of the JCR specification. Several new unit tests were added that verify these behaviors. These new tests all failed prior to these fixes, but they all pass now. (Note this clearly shows the incomplete coverage of the TCK versioning tests.) All unit and integration tests pass with these changes.
…CND files Previously, the CND files were being read but any problems during the reading were not reported and were simply ignored. Some errors cause the reader to abort reading and to have successfully read in no node types, so registration appeared to do nothing while hiding the errors. With these changes, the errors and warnings are included in a thrown exception; if there are no errors and only warnings, the warnings are simply logged. All unit and integration tests pass.
…side finally construct
…arch multiple times The fix was part of the #207 pull request, which basically removed explicit synchronization around the LuceneSearchProcessor and Engine. In addition: - the lucene version was updated from 3.1.0 to 3.4.0 - the LuceneSearchSession was updated to avoid the possible loss of content when indexing the same content in the same workspace from multiple threads