Clone Tools
  • last updated a few minutes ago
Constraints: committers
Constraints: files
Constraints: dates
MODE-1343 Changed descriptions in POM files, removed unused code

Several of the descriptions in the POM files of the sequencer modules were changed

to be more consistent and easily readable in the Maven results. The old descriptions

came from 2.x and have not been changed for quite a while. But the new descriptions

seem to work better and provide more readable Maven output. Also corrected the parent

coordinates in the text connector.

Removed several of the 'extensions/modeshape-sequencer-*' directories that were

recently converted. These older directories are no longer used.

    • -112
    • +0
    • -13
    • +0
  1. … 63 more files in changeset.
Changed versions to prepare for 2.7-SNAPSHOT development

  1. … 77 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.
Changed versions in POMs to '2.6-SNAPSHOT'

  1. … 65 more files in changeset.
MODE-33 Minor corrections to documentation

  1. … 2 more files in changeset.
MODE-33 Added WSDL 1.1 sequencer

Added a new sequencer module for parsing and extracting information from Web Service Definition Language (WSDL) 1.1 files. The structure of the content derived from the WSDL files is based upon the S-RAMP WSDL and SOAPWSDL models, although the structure adds a fair amount of additional information and detail.

Both unit and Integration tests were added for this new sequencer, and the sequencer was added to the JBoss AS kit. All unit and integration tests pass with these changes.

The Reference Guide was updated to describe the new WSDL sequencer, and a few corrects were made to include references to the XSD, WSDL and S-RAMP sequencer modules earlier in the document.

    • -0
    • +44
    • -0
    • +114
    • -0
    • +312
    • -0
    • +248
    • -0
    • +112
    • -0
    • +13
  1. … 47 more files in changeset.