ModeShape

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
MODE-2081 Changed the license for ModeShape code to ASL 2.0.

  1. … 106 more files in changeset.
MODE-2081 Changed the license for ModeShape code to ASL 2.0.

  1. … 145 more files in changeset.
MODE-1683 Added a method for retrieving the last record of a journal. Changed the signature of the methods which used long timestamps to use DateTime(s) and removed unnecessary conversions to UTC.

MODE-1683 Created a time-based sequence

Added a time-based, non-monotonically increasing unique sequence of long values that

can be used in the journal as primary keys for JournalRecord instances so that:

1. they are ordered based upon the sequence in which they arrive

2. we can find the JournalRecords that were added within some time range

MODE-1683 Simplified message consuming & receiving; updated delta reconciliation implementation and MapDB version to 0.9.8.

    • -0
    • +24
    /deploy/jbossas/kit/jboss-eap61/org/mapdb/0.9.8/module.xml
  1. … 5 more files in changeset.
Ignored failing test

Fixed tests which assert repository version (was 3.x is now 4.x).

Changed version to 4.0-SNAPSHOT in preparation for the 4.0 releases.

    • -1
    • +1
    /boms/modeshape-bom-remote-client/pom.xml
  1. … 49 more files in changeset.
'Release: update versions for modeshape-3.7.1.Final'

    • -1
    • +1
    /boms/modeshape-bom-remote-client/pom.xml
  1. … 49 more files in changeset.
Updated release notes for 3.7.1.Final

MODE-2092 Added back 3.6.0.Final compatible dependencies.

    • -0
    • +304
    /boms/modeshape-bom-embedded/pom.xml
    • -0
    • +105
    /boms/modeshape-bom-remote-client/pom.xml
MODE-2092 Updated all the BOMs to include the javax.jcr dependency and also the EAP bom to include the JBoss EAP BOMs in order to offer more dependencies which match those in EAP.

    • -0
    • +30
    /boms/modeshape-bom-jbosseap/pom.xml
    • -0
    • +6
    /boms/modeshape-bom-remote-client/pom.xml
MODE-2092 Added community information to BOMs, which is required by the JBoss Maven repository manager.

Deployment to the JBoss Maven repository is blocked without this information.

    • -0
    • +55
    /boms/modeshape-bom-embedded/pom.xml
    • -0
    • +57
    /boms/modeshape-bom-jbosseap/pom.xml
    • -0
    • +57
    /boms/modeshape-bom-remote-client/pom.xml
MODE-2092 Updated the embedded BOM and added back modeshape-jcr's optional dependencies so that a certain version can be enforced for clients of the BOM. This should make it easier for clients to get the "correct version" of optional components which ModeShape can be configured with in embedded mode.

    • -0
    • +305
    /boms/modeshape-bom-embedded/pom.xml
'Release: update versions for modeshape-3.7.0.Final'

    • -1
    • +1
    /boms/modeshape-bom-remote-client/pom.xml
  1. … 49 more files in changeset.
Updated release notes for 3.7.0.Final

MODE-2131 Updated the copyright date to 2014.

    • -1
    • +1
    /modeshape-jca/src/main/assembly/COPYRIGHT.txt
MODE-2129 Fixed the deployment of the CMIS webapp inside EAP. The solution was to avoid using the default EAP WS stack (which uses CXF) since the CMIS webapp already has pre-packaged the RI jars. In addition, reverted the changes from MODE-1913 since not using the default EAP WS stack fixes the restart issue as well.

MODE-2125 Implemented additional methods in DatabaseMetaData implementation

Teiid requires us to implement several more methods in our DatabaseMetaData

implementation, so that was done. Also fixed a bug in the getColumns(...)

method that expected the column name pattern parameter to be null, when null

should be allowed.

MODE-2126 Corrected NodeIterator.hasNext() to never advance

Turns out that, in some cases, calling `iterator.hasNext()` multiple times before calling

`iterator.next()` incorrectly advanced the iterator when it should not have. Most cases

were fine, but it was a problem when the following two conditions were met:

1. new children were added to the parent node and these were not yet saved; and

2. the iterator was obtained to find nodes with names that matched a specific

pattern (e.g., `node.getNodes(namePattern)`)

This commit adds several test cases (one of which replicated the problem, while all the

others tests show the problem is limited to the above conditions) and that fixes the problem.

Fixed JavaDoc errors by correcting imports

MODE-2124 Changed the code so that child node re-indexing (on update of the parent) is only performed when the path of the parent has changed. Also, based on additional CPU usage profiling, removed a String.intern call.

'Release: update versions for modeshape-3.6.1.Final'

    • -2
    • +2
    /boms/modeshape-bom-remote-client/pom.xml
  1. … 51 more files in changeset.
Tests marked with @SkipLongRunning still run during -Passembly, so ignoring this very resource-intensive load test.

Tests marked with @SkipLongRunning still run during -Passembly, so ignoring this very resource-intensive load test.

Changed release notes

Reverted version back to SNAPSHOT, which will be set properly during the release process.

    • -2
    • +2
    /boms/modeshape-bom-remote-client/pom.xml
  1. … 51 more files in changeset.
MODE-2123 Changed the code so that new nodes never try to find themselves in the workspace cache.

Also fixed some resulting regressions for specific situations.

MODE-2123 Changed the code so that new nodes never try to find themselves in the workspace cache.

Also fixed some resulting regressions for specific situations.

MODE-2122 Added some retry logic in case we're reading the parent's ChildReference objects while it is being modified

Most of the time, this shouldn't be a problem. But the changes make the code tolerant of such rare concurrent modifications

by simply retrying. There is almost no extra cost to doing this.

The stress test added in the previous commit used to periodically demonstrate the concurrent modification exception.

After the changes, the exception no longer occurs.