modeshape-jcr-api

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Changed version to 4.3-SNAPSHOT.

  1. … 64 more files in changeset.
'Release: update versions for modeshape-4.2.0.Final'

  1. … 64 more files in changeset.
MODE-2383 Fixed the way binary distributions are built so that there is no need to install *-with-dependency artifacts in the Maven repository.

  1. … 24 more files in changeset.
Updated POM versions to 4.2-SNAPSHOT

  1. … 64 more files in changeset.
MODE-2383 Added back "examples" to the binary distribution and made sure none of the ZIP assemblies get attached & deployed to Nexus.

  1. … 21 more files in changeset.
'Release: update versions for modeshape-4.1.0.Final'

  1. … 64 more files in changeset.
JcrTools authorization fix

- Patch for findOrCreateChild to avoid getting ancestral nodes that aren't necessary for the current operation, because in ACL context AccessDeniedException would be thrown if the user doesn't have access to those ancestors.

- Created a test to verify lacking ancestor read permission does not prevent findOrCreateChild from creating nodes.

  1. … 1 more file in changeset.
'Release: update versions for modeshape-3.8.1.Final'

  1. … 64 more files in changeset.
Updated version to 4.1-SNAPSHOT

  1. … 64 more files in changeset.
'Release: update versions for modeshape-4.0.0.Final'

  1. … 64 more files in changeset.
'Release: update versions for modeshape-4.0.0.Beta2'

  1. … 64 more files in changeset.
MODE-2301 Added support for indexes to be updated synchronously or asynchronously

Prior to this commit, all updates to the indexes in the 4.0 codebase were asynchronous. That means that

the Session.save() method added the ChangeSet describing the session's changes onto the event bus and

then returned. All index updates were done in separate listener threads on the event bus, so it's entirely

possible (and perhaps likely) that any updates to the indexes happen after the client's call to Session.save()

returned. The net effect is that the client might make changes and immediately issue a query that would not

find the recently-saved changes. Additionally, there was no way for the client to know when the indexes would

be updated.

With this commit, it is possible to define whether each index is updated synchronously before the

the Session.save() returns, or asynchronously so that index updates are made in a separate thread.

This commit changes the default behavior of the index updates to be *synchronous*.

In a cluster, any changes made on one process are sent via the change bus to the other processes,

and the indexes in those other processes are always updated asynchronously. In other words, if an

index provider keeps copies of the indexes on every process, then only the local indexes are updated

synchronously before save returns -- and that Session.save() does not wait until the indexes in the other

processes are updated.

In order to properly implement this, a small change was made to the ChangeBus to expand the semantic concept

of an "in-thread" listener. Prior to this, "in-thread" meant that the listener only received locally-originating

change sets. Now, it's still possible to do this (and the journal uses this older behavior), but it's also

possible to register a listener such that locally-originating change sets are handled in-thread while remotely

originating change sets are handled asynchronously.

  1. … 19 more files in changeset.
Changed components versions to 2.8.2.GA.

  1. … 67 more files in changeset.
MODE-2151 Added support for CHILDCOUNT dynamic operand

Pretty basic support that should prove quite useful in certain situations. This may be relatively

expensive when the repository has nodes with lots of children since it requires loading the parent

node's child references in order to obtain the count. The CHILDCOUNT criteria would therefore work

much better/faster as filtering criteria in a query that already defines criteria that indexes can

use.

    • -0
    • +32
    ./src/main/java/org/modeshape/jcr/api/query/qom/ChildCount.java
  1. … 16 more files in changeset.
MODE-2286 Made it easier to use the ModeShape public API for queries

  1. … 1 more file in changeset.
'Release: update versions for modeshape-4.0.0.Beta1'

  1. … 64 more files in changeset.
MODE-2160 Incorporated recent comments and added validation of IndexDefinintions before registration.

  1. … 10 more files in changeset.
MODE-2160 Completed the first stab at a local index provider. There are only a few very limited test cases, but they do pass and show that the provider is able to be included in the query plan, properly selected for use, and properly used during query execution.

  1. … 54 more files in changeset.
MODE-1671 Added 'mode:id' pseudocolumn for JCR-SQL2 queries

It is now possible to use the 'mode:id' pseudocolumn that exists on all selectors

to obtain the javax.jcr.Node.getIdentifier() value. It can be used in WHERE constraints

and JOIN criteria.

    • -0
    • +33
    ./src/main/java/org/modeshape/jcr/api/query/qom/NodeId.java
  1. … 19 more files in changeset.
'Release: update versions for modeshape-4.0.0.Alpha4'

  1. … 65 more files in changeset.
Updated artifacts version to 3.8.1.GA and changed the GitConnector tests to reflect the structure of the https://github.com/jboss-integration/modeshape repository.

  1. … 67 more files in changeset.
'Release: update versions for modeshape-3.8.0.Final'

  1. … 64 more files in changeset.
'Release: update versions for modeshape-4.0.0.Alpha3'

  1. … 65 more files in changeset.
'Release: update versions for modeshape-3.7.4.Final'

  1. … 64 more files in changeset.
Changed snapshot version to 3.7-SNAPSHOT to more accurately reflect the branch.

  1. … 64 more files in changeset.
'Release: update versions for modeshape-3.7.3.Final'

  1. … 64 more files in changeset.
Changed to 3.8-SNAPSHOT

  1. … 64 more files in changeset.
MODE-2097, MODE-2169, MODE-2197 Integrated the latest version of the jboss-integration BOM. This commit includes changes for multiple different issues that snowballed: - packaging Javadocs in a zip - updating Apache POI In addition, after integrating the BOM a number of unit tests had to be updated to reflect changes in dependencies both from a functionality perspective and from a deprecation perspective. The most significant change there was the rewriting of the ConnectorTestCase (modeshape-jca) because the new versions of Arquillian + IronJacamar hold filelocks on Windows: https://issues.jboss.org/browse/JBJCA-1027

  1. … 93 more files in changeset.
'Release: update versions for modeshape-4.0.0.Alpha2'

  1. … 65 more files in changeset.
MODE-2160 Refactored the query engine and index provider SPI.

Changed how index providers are initialized, changed the indexing to use only events, changed the reindexing mechanism to use a much simplified IndexWriter, and added a partial LocalIndex and provider implementation (still needs work).

    • -0
    • +146
    ./src/main/java/org/modeshape/jcr/api/index/IndexDefinition.java
    • -0
    • +95
    ./src/main/java/org/modeshape/jcr/api/index/IndexManager.java
  1. … 107 more files in changeset.