modeshape-connector-disk

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Changed components versions to 2.8.2.GA.

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

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

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

  1. … 70 more files in changeset.
MODE-1414 (related): promote version #'s in 2.5.x to 2.5.4.GA for BZ-786561 Roll up patch fro EDS_5.2_20120320

  1. … 68 more files in changeset.
Changed version to SNAPSHOT following release

  1. … 74 more files in changeset.
Changed the '2.8-SNAPSHOT' artifact version to '2.8.1.GA' for use in the product.

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

  1. … 70 more files in changeset.
MODE-1368 Removed all legacy modules no longer needed in 3.x

ModeShape 3.x will not need a number of the 2.x modules. In particular:

- since 3.x will only have an AS7 kit, the AS5 or AS6 artifacts were removed

- all the connectors were removed, since they're no longer used

- the connector benchmark tests module was removed, replaced by our new

performance test suite

- the JPA DDL generator utility has been removed

- the 'modeshape-graph', 'modeshape-repository', 'modeshape-search-lucene'

and 'modeshape-clustering' modules have all been removed, since the new

'modeshape-jcr' module no longer uses them

- the DocBook modules were removed and are replaced by the Confluence space

- the two JDBC modules were moved out of the 'utils' directory to top-level modules

The build still works, but not all components have been included in the build.

This is because the query functionality doesn't yet work, so quite a few web

and JDBC driver modules all depend on this.

The assembly profile has not yet been changed or corrected.

  1. … 3639 more files in changeset.
Changed version to 2.8-SNAPSHOT after releasing 2.7.0.Final

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

  1. … 76 more files in changeset.
MODE-1353: promote version #'s in 2.5.x to 2.5.3.GA for SOA-3656

  1. … 68 more files in changeset.
MODE-1305 Remove unused i18n methods

- also a small refactoring of the I18n class

  1. … 23 more files in changeset.
MODE-1305 Remove unused i18n methods

- also a small refactoring of the I18n class

  1. … 23 more files in changeset.
MODE-1298 Added more unit tests to help diagnose

Added several unit tests, plus some 'toString', 'equals', and 'hashCode' methods to the ValueReferences

class and a 'toString' method to the ValueReference class.

This commit includes no changes that attempt to fix the problem.

MODE-1298 Added more unit tests to help diagnose

Added several unit tests, plus some 'toString', 'equals', and 'hashCode' methods to the ValueReferences

class and a 'toString' method to the ValueReference class.

This commit includes no changes that attempt to fix the problem.

  1. … 1 more file in changeset.
Changed versions to prepare for 2.7-SNAPSHOT development

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

  1. … 69 more files in changeset.
Changed version to 2.5.2.GA, in preparation for release.

  1. … 73 more files in changeset.
MODE-1289 New approach for storing/caching JCR content

This is the first commit to start the 3.0 effort, which involves a major change to how

the JCR layer stores and caches information. The new approach is based upon Infinispan and uses

Infinispan's cache loaders for persistence, and JSON-like documents (that are in-memory

structures not needing to parsed/written) are used to store information for each node.

There are several new Maven modules:

- modeshape-jcr-redux

- modeshape-schematic

The 'modeshape-jcr-redux' module will eventually replace the 'modeshape-jcr' module once

the implementation is far-enough along. And the 'modeshape-schematic' module will likely

move into the Infinispan project, so that needs to remain separate.

Although it may seem strange and unkempt to have the new JCR implementation in a new module,

doing so means that we can continue to rebase from 'master' (and the 2.7 work) for at least

some time. When the new module becomes complete enough, we'll move it and replace the

existing 'modeshape-jcr' module. It's also convenient to have both the old and new implementations

around in the same codebase.

The build was changed to focus upon the (few) modules that are oriented around the new

implementation. So the following can be used to build the newer codebase:

mvn clean install

However, the build has a new Maven profile called "legacy" that can be used to build the

old modules. We kept this to make sure that any rebasing can be compiled and verified.

For example, to build everyhing, including the new modules and the 2.x-style modules,

use the following command:

mvn clean install -Plegacy

As the newer 'modeshape-jcr-redux' progresses and other modules (e.g., sequencers, web,

jboss, text extractors) are converted to use the new module, they should be moved

from the 'legacy' profile into the main set of modules in the top-level 'pom.xml'

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

  1. … 69 more files in changeset.
'Release: update versions for modeshape-2.6.0.Beta1'

  1. … 69 more files in changeset.
MODE-1212 Clean up unit/integration tests that uses SecurityContextCredentials

Attached patch removes all test uses of SecurityContextCredentials and replaces custom RepositoryContext implementations with MockRepositoryContext where possible. All tests pass.

  1. … 24 more files in changeset.
MODE-1212 Clean up unit/integration tests that uses SecurityContextCredentials

Attached patch removes all test uses of SecurityContextCredentials and replaces custom RepositoryContext implementations with MockRepositoryContext where possible. All tests pass.

  1. … 24 more files in changeset.
MODE-1193, MODE-1203 Corrected compiler warnings

  1. … 16 more files in changeset.
MODE-1193, MODE-1203 Corrected compiler warnings

  1. … 16 more files in changeset.
MODE-1181 Add Benchmark to track connector performance over time

Added simple framework for benchmark testing of connectors. The benchmark runs a series of tests against

all of the connectors configured within a single ModeShapeEngine, and then generates an HTML report

with a graph for each test showing the performance of each connector.

  1. … 7 more files in changeset.
MODE-1181 Add Benchmark to track connector performance over time

Added simple framework for benchmark testing of connectors. The benchmark runs a series of tests against

all of the connectors configured within a single ModeShapeEngine, and then generates an HTML report

with a graph for each test showing the performance of each connector.

  1. … 7 more files in changeset.
MODE-1203 Support Node Caching in Connectors

The attached patch generalizes the earlier work towards a cache for the disk-based connector into a generic cache framework that can be used for the DiskSource, FileSystemSource, JdbcMetadataSource, and the SvnRepositorySource. The InMemoryRepositorySource, InfinispanSource, and JBossCacheSource were not modified because they already store data in-memory and aren't likely to benefit from a node cache. The JpaSource was not modified because it still uses the old map connector framework. A decision should be made on whether to port that source forward into the new connector framework before caching is added.

A working cache implementation, InMemoryNodeCache is provided along with two working cache policies: InMemoryNodeCache$MapCachePolicy and InMemoryNodeCache$PathCachePolicy. Connectors can use this cache by setting the nodeCachePolicy property on the connector to the classname of one of these implementations and setting the timeToLive property on the _cachePolicy_ (not on the source itself) to the length of time in seconds that nodes should remain in the cache. Nodes are added to the cache on reads and writes. Cache configurations have been added to the Reference Guide for each of the affected connectors.

IMPORTANT: THE CACHE POLICY MUST CORRESPOND TO THE CONNECTOR TYPE. That is, path connectors must use a cache policy that creates caches that implement PathNodeCache, and map connectors must use a cache policy that creates caches that implement NodeCache.

All tests pass.

  1. … 38 more files in changeset.
MODE-1203 Support Node Caching in Connectors

The attached patch generalizes the earlier work towards a cache for the disk-based connector into a generic cache framework that can be used for the DiskSource, FileSystemSource, JdbcMetadataSource, and the SvnRepositorySource. The InMemoryRepositorySource, InfinispanSource, and JBossCacheSource were not modified because they already store data in-memory and aren't likely to benefit from a node cache. The JpaSource was not modified because it still uses the old map connector framework. A decision should be made on whether to port that source forward into the new connector framework before caching is added.

A working cache implementation, InMemoryNodeCache is provided along with two working cache policies: InMemoryNodeCache$MapCachePolicy and InMemoryNodeCache$PathCachePolicy. Connectors can use this cache by setting the nodeCachePolicy property on the connector to the classname of one of these implementations and setting the timeToLive property on the _cachePolicy_ (not on the source itself) to the length of time in seconds that nodes should remain in the cache. Nodes are added to the cache on reads and writes. Cache configurations have been added to the Reference Guide for each of the affected connectors.

IMPORTANT: THE CACHE POLICY MUST CORRESPOND TO THE CONNECTOR TYPE. That is, path connectors must use a cache policy that creates caches that implement PathNodeCache, and map connectors must use a cache policy that creates caches that implement NodeCache.

All tests pass.

  1. … 38 more files in changeset.