ModeShape

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
MODE-1246 Removed colons (not allowed on Windows) from worksapce name in WorkspaceConnectorTest

MODE-1246 Removed colons (not allowed on Windows) from worksapce name in WorkspaceConnectorTest

Debugging test case that fails on server.

MODE-1243 Minor correction to Reference Guide.

MODE-1243 Minor correction to Reference Guide.

MODE-1243 JndiRepositoryFactory should support registering engine in JNDI

The JndiRepositoryFactory implementation should support registering the ModeShape engine into JNDI if the repository name is empty or not provided. This change would allow using the factory to configure Glassfish or Tomcat by registering the engine in JNDI so that JCR-2.0-style lookup are possible.

See also MODE-1242 for the change to make RepositoryFactory recognize JNDI URLs to Repository instances, not just ModeShape engine instances.

All unit and integration tests pass with this change.

MODE-1243 JndiRepositoryFactory should support registering engine in JNDI

The JndiRepositoryFactory implementation should support registering the ModeShape engine into JNDI if the repository name is empty or not provided. This change would allow using the factory to configure Glassfish or Tomcat by registering the engine in JNDI so that JCR-2.0-style lookup are possible.

See also MODE-1242 for the change to make RepositoryFactory recognize JNDI URLs to Repository instances, not just ModeShape engine instances.

All unit and integration tests pass with this change.

MODE-1242 RepositoryFactory should support JNDI URL to Repository instance

The JcrRepositoryFactory implementation should support JNDI URLs that point to a Repository instance rather than a ModeShape engine.

When deploying ModeShape to Glassfish or Tomcat, using JndiRepositoryFactory will often be used to register specific Repository instances in JNDI, making the JCR-2.0-style lookup impossible without this change.

All unit and integration tests pass with this change.

MODE-1242 RepositoryFactory should support JNDI URL to Repository instance

The JcrRepositoryFactory implementation should support JNDI URLs that point to a Repository instance rather than a ModeShape engine.

When deploying ModeShape to Glassfish or Tomcat, using JndiRepositoryFactory will often be used to register specific Repository instances in JNDI, making the JCR-2.0-style lookup impossible without this change.

All unit and integration tests pass with this change.

MODE-1241 Corrected duplicate serialization of properties in JPA source

The JPA source was handling UpdatePropertyRequests by iterating through its properties and then removing or

updating the property on the JPA node. Each time a property was modified (removed or added or updated), all

of the nodes properties were serialized. This not only is WAY more work than needed, but it causes a

problem when a file backed Binary value is used (since the first serialization closes the backing stream,

and subsequent serialization attempts to use the closed stream).

This was fixed by simply changing how the UpdatePropertyRequests are handled in MapRequestProcessor to

update and remove all of the appropriate properties in one shot, via a modified 'setProperties' method on

the MapNode, DefaultMapNode, and JpaNode. Because the MapNode interface was changed, several other uses

required modification.

Van's test case was able to duplicate the problem prior to these changes. After these changes, all

unit and integration tests pass.

    • -0
    • +1036
    /modeshape-integration-tests/src/test/resources/test.txt
MODE-1241 Corrected duplicate serialization of properties in JPA source

The JPA source was handling UpdatePropertyRequests by iterating through its properties and then removing or

updating the property on the JPA node. Each time a property was modified (removed or added or updated), all

of the nodes properties were serialized. This not only is WAY more work than needed, but it causes a

problem when a file backed Binary value is used (since the first serialization closes the backing stream,

and subsequent serialization attempts to use the closed stream).

This was fixed by simply changing how the UpdatePropertyRequests are handled in MapRequestProcessor to

update and remove all of the appropriate properties in one shot, via a modified 'setProperties' method on

the MapNode, DefaultMapNode, and JpaNode. Because the MapNode interface was changed, several other uses

required modification.

Van's test case was able to duplicate the problem prior to these changes. After these changes, all

unit and integration tests pass.

    • -0
    • +1036
    /modeshape-integration-tests/src/test/resources/test.txt
MODE-1150 Upgraded to SLF4J 1.6.1

Changed the SLF4J dependency from 1.5.11 to 1.6.1, including all of the documentation and the various web and jboss related modules.

Note that 1.6.x has changed its API slightly, and this breaks some libraries. Therefore, 1.6.x has to be used for all SLF4J-related libraries; one critical issue proved to be the "org.slf4j:jcl-over-slf4j" artifact that apparently is no longer needed (or at least needs to be the same version, and because RESTEasy had an explicit dependency on the then there was some work in excluding it from the web- and jboss- related ModeShape modules.

All unit and integration tests pass with these changes.

    • -6
    • +13
    /web/modeshape-web-jcr-rest/pom.xml
Upgrade Logback to 0.9.29 in Examples

MODE-931 Corrected offset projection behavior

Changed the logic in the JoinRequestProcessor to correctly handle offset projections (along with other projections)

when processing ReadNodeRequests.

A new integration test was added, and all unit and integration tests pass with these changes.

    • -0
    • +44
    /modeshape-integration-tests/src/test/resources/config/configRepositoryForFederatedConnector.xml
MODE-931 Corrected offset projection behavior

Changed the logic in the JoinRequestProcessor to correctly handle offset projections (along with other projections)

when processing ReadNodeRequests.

A new integration test was added, and all unit and integration tests pass with these changes.

    • -0
    • +44
    /modeshape-integration-tests/src/test/resources/config/configRepositoryForFederatedConnector.xml
Corrected DocBook error in query examples section.

Corrected DocBook error in query examples section.

Slightly improved the query examples section.

Slightly improved the query examples section.

MODE-1237 Corrected handling of empty results from subquery.

Corrected how the query execution handles putting the subquery results into the variables, so that even

an empty array of tuples is put into the variables. Without this, when executing and using the subquery results,

the execution logic gets a null for the subquery 'variable' and records an error rather than just using an empty

array.

All unit and integration tests pass with these changes.

MODE-1237 Corrected handling of empty results from subquery.

Corrected how the query execution handles putting the subquery results into the variables, so that even

an empty array of tuples is put into the variables. Without this, when executing and using the subquery results,

the execution logic gets a null for the subquery 'variable' and records an error rather than just using an empty

array.

All unit and integration tests pass with these changes.

MODE-1236 Added INFO-level log messages for reindexing

Changed the existing log messages used during the beginning and end of the reindexing process from debug-level to info-level, and adjusted the messages to include the repository name (and workspace name if an entire workspace is being reindexed).

All unit and integration tests pass.

MODE-1236 Added INFO-level log messages for reindexing

Changed the existing log messages used during the beginning and end of the reindexing process from debug-level to info-level, and adjusted the messages to include the repository name (and workspace name if an entire workspace is being reindexed).

All unit and integration tests pass.

Corrected description in Reference Guide.

Corrected description in Reference Guide.

MODE-1234 Corrected indexing and querying of BOOLEAN properties

Query nodes based upon custom node types with BOOLEAN properties did work, whereas querying nodes based upon built-in node types with BOOLEAN properties did not work. This fix corrects one error in the way properties are indexed, and another in how constraints against BOOLEAN properties are transformed into Lucene queries. These two errors cancelled each other out for properties on custom node types, but caused issues with properties on built-ins.

Once this fix is applied (through an upgrade to 2.6.0.Final, the indexes should be rebuilt to correct the existing indexes.

All unit and integration tests pass, including several new tests written to duplicate/verify the problem.

    • -0
    • +17
    /modeshape-jcr/src/test/resources/notionalTypes.cnd
MODE-1234 Corrected indexing and querying of BOOLEAN properties

Query nodes based upon custom node types with BOOLEAN properties did work, whereas querying nodes based upon built-in node types with BOOLEAN properties did not work. This fix corrects one error in the way properties are indexed, and another in how constraints against BOOLEAN properties are transformed into Lucene queries. These two errors cancelled each other out for properties on custom node types, but caused issues with properties on built-ins.

Once this fix is applied (through an upgrade to 2.6.0.Final, the indexes should be rebuilt to correct the existing indexes.

All unit and integration tests pass, including several new tests written to duplicate/verify the problem.

    • -0
    • +17
    /modeshape-jcr/src/test/resources/notionalTypes.cnd
'Release: update versions for modeshape-2.6.0.Beta2'

  1. … 55 more files in changeset.
Updated release notes

Updated release notes