ModeShape

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
MODE-1587 - Updated the modeshape distribution so that it runs on a AS7.2 server and re-enabled the integration tests modules. However, for a local build to work, one needs for the time being a locally installed (via Maven) version of AS7.2.

In the process of updating the kit, a couple of other things were updated:

- exception processing around WritableSessionCache#persistChanges

- logging of exceptions / errors in the ModeShape Webdav Servlet

Fix broken tests.

MODE-1832: ModeShape CMIS component has bug in JcrService

Corrects for use of ">" and adds a basic test case.

https://issues.jboss.org/browse/MODE-1832

MODE-1764 - Updated the AS7 kit that will be provided as part of 3.2 - the former 7.1.1.kit has been removed (together will assemblies) because ISPN 5.2 is not compatible with AS7.1.1 - removed the modeshape-integration-tests folder as that was ported from 2.x and either the corresponding tests have been ported in various other places in 3.x or they no do apply anymore (connectors) - changed our AS7 distribution kit to as72 - since integration with AS7.2.0 is still WIP, the integration modules have been commented out

  1. … 379 more files in changeset.
MODE-1763 - Updated Infinispan XML schema to 5.2 and logging to turn off useless INFO messages.

  1. … 25 more files in changeset.
MODE-1763, MODE-1304 - Updated the ISPN dependency to 5.2.1 and Hibernate Search/Lucene to 4.2/3.6.

Because the new version of Infinispan does not allow by default duplicate MBeans with the same name, the tests had to be updated to specifically turn this option on for each used caches.

  1. … 22 more files in changeset.
MODE-1833 - JQOM Wildcard Query fails with Column 'null' does not exist on the table

Fixed with testcase.

Updated POMs for next SNAPSHOT version

    • -2
    • +2
    /boms/modeshape-bom-remote-client/pom.xml
  1. … 48 more files in changeset.
Update bin/jira.py

Update bin/jira.py

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

    • -2
    • +2
    /boms/modeshape-bom-remote-client/pom.xml
  1. … 48 more files in changeset.
Updated release scripts to deal with JIRA accounts that have no last name

Updated release scripts to deal with JIRA accounts that have no last name

Updated release notes

Changed the version to 3.1.3-SNAPSHOT

    • -2
    • +2
    /boms/modeshape-bom-remote-client/pom.xml
  1. … 48 more files in changeset.
MODE-1830 Corrected the purging of workspace caches in a cluster

Before this fix, when a change was made via a WritableSessionCache,

any changes persisted to the store were also used to directly purge

any previously-cached node representations from the corresponding

WorkspaceCache. Thus, when the RepositoryCache received the changes,

it simply forwarding them to all workspaces except the one in which

the changes originated.

However, in a clustered environment, the changes originate on one

process and are sent to all other processes. The logic described

above works fine in the same process in which the changes originated,

but it doesn't correctly propagate the changes in the other processes.

The fix was pretty simple: determine if the changes came from the same

process. If so, the use the current logic. If not, always forward the

changes to all WorkspaceCache instances.

I also modified the ClusteredRepositoryTest to look in process A for

nodes changed in process B. This failed before the logic was fixed,

and now works with the fix.

MODE-1830 Corrected the purging of workspace caches in a cluster

Before this fix, when a change was made via a WritableSessionCache,

any changes persisted to the store were also used to directly purge

any previously-cached node representations from the corresponding

WorkspaceCache. Thus, when the RepositoryCache received the changes,

it simply forwarding them to all workspaces except the one in which

the changes originated.

However, in a clustered environment, the changes originate on one

process and are sent to all other processes. The logic described

above works fine in the same process in which the changes originated,

but it doesn't correctly propagate the changes in the other processes.

The fix was pretty simple: determine if the changes came from the same

process. If so, the use the current logic. If not, always forward the

changes to all WorkspaceCache instances.

I also modified the ClusteredRepositoryTest to look in process A for

nodes changed in process B. This failed before the logic was fixed,

and now works with the fix.

MODE-1829 Re-enabled several query tests

MODE-1829 Re-enabled several query tests

MODE-1763 Removed the @Ignore from an integration test

Removed the @Ignore from the JDBCRepositoryIntegrationTest, which had

to be added to the changes for MODE-1826 since the fix for

MODE-1769 has not yet been corrected but will be when Infinispan

5.2.1.Final is used.

MODE-1826 MODE-1769 MODE-1763 Temporarily ignored the JDBC smoke test

MODE-1826 - Added an integration smoke test which uses a write-behind, JDBC cache store

MODE-1826 - Added an integration smoke test which uses a write-behind, JDBC cache store

MODE-1823 - Fixed the WebDAV servlet to use UTF-8 encoding in paths and also to generate full links when displaying the contents of folders.

MODE-1823 - Fixed the WebDAV servlet to use UTF-8 encoding in paths and also to generate full links when displaying the contents of folders.

MODE-1828 - ConstraintViolationException when updating the definition of the same node in a session

Fix the issue by making sure that nodeTypes with the same name is actually updated properly in the cache.

    • -0
    • +7
    /modeshape-jcr/src/test/resources/cnd/nodeTypeChange-next.cnd
MODE-1828 - ConstraintViolationException when updating the definition of the same node in a session

Fix the issue by making sure that nodeTypes with the same name is actually updated properly in the cache.

    • -0
    • +7
    /modeshape-jcr/src/test/resources/cnd/nodeTypeChange-next.cnd
MODE-1822 Added tests that use Atomikos transaction manager

Other fixes for MODE-1819 actually fixed the problem, while this

change only adds test cases and test dependencies on Atomikos to

verify the expected behavior now works. Also added similar tests

that use the JBoss Transactions library.

MODE-1822 Added tests that use Atomikos transaction manager

Other fixes for MODE-1819 actually fixed the problem, while this

change only adds test cases and test dependencies on Atomikos to

verify the expected behavior now works. Also added similar tests

that use the JBoss Transactions library.

MODE-1827 - NullPointerException in RepositoryQueryManager

Null check in case the node no longer exist in the cache.