modeshape-sequencer-xsd

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.
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.
Changed versions in POMs to '2.5.1.GA'

  1. … 65 more files in changeset.
Changed versions in POMs to '2.6-SNAPSHOT'

  1. … 65 more files in changeset.
Changed versions in POMs to '2.5.1-SNAPSHOT'

  1. … 65 more files in changeset.
MODE-32 Removed unused code

A single 'printStackTrace()' call was removed (per the review), and also the JavaBean property detailing

the local cache of XSDs was removed, as it was no longer used.

All unit tests pass with these changes.

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
    • +16
    ./src/test/resources/stockQuote.xsd
  1. … 57 more files in changeset.
MODE-32 Implemented sequencer for XML Schema Documents

Created a new 'modeshape-sequencer-xsd' module that parses and sequences XSDs. It uses the Eclipse XSD library (which is based on EMF). The XSD sequencer outputs a structure that was designed to mirror the proposed S-RAMP spec (which is currently still in OASIS Technical Committee), and so there is a S-RAMP namespace and a few base node types defined in a new 'modeshape-sequencer-sramp' module.

I had initially tried and would have preferred to use the XSOM parser library (which has a far better API and actually follows Maven best practices), but had severe trouble resolving imports/includes where Eclipse XSD appears to work much better so far.

All unit and integration tests pass. Also, the reference guide was updated with a new chapter for the XSD sequencer.

    • -0
    • +44
    ./src/main/java/org/modeshape/sequencer/xsd/XsdI18n.java
    • -0
    • +74
    ./src/main/java/org/modeshape/sequencer/xsd/XsdLexicon.java
    • -0
    • +956
    ./src/main/java/org/modeshape/sequencer/xsd/XsdReader.java
    • -0
    • +60
    ./src/main/java/org/modeshape/sequencer/xsd/XsdResolvers.java
    • -0
    • +94
    ./src/main/java/org/modeshape/sequencer/xsd/XsdSequencer.java
    • -0
    • +29
    ./src/main/java/org/modeshape/sequencer/xsd/package-info.java
    • -0
    • +258
    ./src/main/resources/org/modeshape/sequencer/xsd/xsd.cnd
    • -0
    • +33
    ./src/test/java/org/modeshape/sequencer/xsd/XsdI18nTest.java
    • -0
    • +3
    ./src/test/resources/definitiveXmlSchema/README.txt
    • -0
    • +17
    ./src/test/resources/definitiveXmlSchema/chapter01.xsd
    • -0
    • +24
    ./src/test/resources/definitiveXmlSchema/chapter03env.xsd
  1. … 77 more files in changeset.