modeshape-integration-tests

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.
MODE-1623 - Updated the mode:isolationLevel flag fix and added an ignored unit test which can be run to reproduce this issue.

  1. … 2 more files in changeset.
MODE-1561 - Updated the TikaTextExtractor to support a "writeLimit" property which is passed down to Tika. If absent, the default Tika limit of 100k characters is used.

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

  1. … 70 more files in changeset.
MODE-1616 Changed some of the test that use HSQLDB to use an in-memory DB

MODE-1585 - Fixed checkout of nodes when a federated source is used

  1. … 1 more file in changeset.
MODE-1559 - Updated the MSOffice sequencer so that the "mode:derived" properties are set on the root of the sequencing output.

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

  1. … 70 more files in changeset.
MODE-1490 - Added checks for oderBefore: if the source and destination are the same, no changes should be performed.

    • -0
    • +20
    ./src/test/resources/memory/configEmptyRepository.xml
  1. … 2 more files in changeset.
MODE-1553 - Removed fixxme comment from test CND file

    • -1
    • +0
    ./src/test/resources/memory/nodetypes.cnd
MODE-1553 - Updated the Processor so that the jcr:uuid property is stored as a node property, when the node is created.

    • -2
    • +29
    ./src/test/resources/memory/nodetypes.cnd
  1. … 1 more file in changeset.
MODE-1500 MODE-1501 Corrected AS7 integration (JNDI names and assemblies)

Several issues were identified and corrected. The first was that although the ModeShape engine

(e.g, the 'org.modeshape.jcr.api.Repositories' implementation) was registered in JNDI,

the Repository instances were not correctly being registered and were thus not able to be found

by deployed components. This was rectified, and now the engine and each repository is properly

registered in JNDI.

Secondly, the JNDI names where the engine and repositories are registered were changed to

more closely align with the naming patterns used by other implementations. The engine

is always registered at "jcr" in the "java:" namespace (i.e, "java:/jcr"), while each

repository is registered at "jcr/{repositoryName}" in the "java:" namespace. For example,

the repository named "sample" could be found in JNDI at "java:/jcr/sample" or "jcr/sample".

This conforms to the many examples that configure a JCR repository at "jcr/local"

(where only one repository is used).

Note that the new default JNDI names are different than ModeShape 2.x, which used "jcr/local" as the

location of the engine and "jcr/local/{repositoryName}" as the default location for each

repository. However, should the old style still be needed for a repository, the repository can

be configured with a custom JNDI name.

Thirdly, when a repository is configured to have a custom JNDI name, the repository is registered

under the specified name (as before), but now the repository is still registered under the

'jcr/{repositoryName}' name. This means that code can find the repository under either name.

Fourthly, the assembly for the ModeShape kit was moved from the 'deploy/jbossas' Maven module

(which installed the resulting ZIP into the Maven repository at 'org/modeshape/jbossas/jbossas-{version}-jbossas-7-dist.zip')

and into the "modeshape-distribution" module, which is where the binary and source distributions

are assembled. And the assembly descriptor was moved to the "modeshape-assembly-descriptors"

module (again, where the other assembly descriptors are managed and installed into the Maven repository).

Fifthly, new integration tests were written to verify that EJBs (of various flavors) can

find the ModeShape repositories correctly using the 4 different ways of looking up a repository:

1) looking up a repository in JNDI

2) looking up the Repositories interface and using it to get a named repository

3) using RepositoryFactory with a single URL (e.g., "jndi:jcr/sample" or "jndi:jcr?repositoryName=sample")

4) using RepositoryFactory with a URL to the engine (e.g, "jndi:jcr") and the name of the repository

These new integration tests are in a new Maven module that downloads AS7 and the ModeShape kit

from the Maven repository and unpacks them into the 'target' directory. When Surefire runs,

this managed server is started, the Arquillian tests are run, and then the server is shutdown.

Each Arquillian test involves creating a WAR file that will be deployed by Arquillian to the

running server, running the unit tests, and then undeploying the WAR file. The tests

can also be run with a different profile so that the tests are deployed and executed in

a separate server installation (as specified by the $JBOSS_HOME variable).

Finally, the older "modeshape-integration-tests" module and the new "modeshape-jbossas-integration-tests"

were relocated to a new top-level folder called 'integration' in the source code. Like the other

top-level directories in our codebase, this is also a Maven module that can be used to run

all of the integration tests. And the '-Pintegration' profile was brought back so that

the distributions are not created and the integration tests not run during the normal builds.

Thus, to run a normal developer build (with all the unit tests but none of the integration tests) simply use

mvn clean install

while the following command will build everything, run all the unit tests, build the AS7 assembly, and run the integration tests:

mvn clean install -Pintegration

As before, running an 'assembly' build (used for releases) will build everything, run all the unit tests,

build the AS7, binary, and source assemblies (including JavaDoc), run the integration tests, and run

the demos:

mvn clean install -Passembly

    • -1447
    • +0
    ./src/test/byteman/jcr-performance.txt
  1. … 610 more files in changeset.
MODE-1502 - Added check to the MsOffice sequencer for the case when no thumbnail information is present in the document

  1. … 1 more file in changeset.
MODE-1475 Corrected JQOM query behavior and added TCK tests

Corrected a number of issues with JQOM queries, including how the corresponding string statements

are generated so that they are now valid JCR-SQL2 statements. Also added the JQOM TCK tests

(not sure why they were excluded), which identified quite a few more. These are all now fixed,

excluding several known and logged issues with the TCK tests themselves.

All unit and integration tests pass with these changes.

  1. … 69 more files in changeset.
MODE-1483 - Fixed erroneous deletion of the parent file when cleaning up content

  1. … 1 more file in changeset.
MODE-1483 - Extra properties files stored via the file system connector are now removed.

The original problem was caused by the incomplete handling for removal of nodes by the FileSystemWorkspace and the fact that the StoreProperties stores additional file & folder properties in external files (external to the file nodes themselves)

  1. … 5 more files in changeset.
'Release: update versions for modeshape-3.0.0.Alpha4'

  1. … 45 more files in changeset.
MODE-1470 - Added the test used in the attempt to reproduce the issue. Since it can't be reproduced atm and the test does take a bit of time to run, it's ignored.

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

  1. … 70 more files in changeset.
MODE-1422 - Fixed the invalid ReferenceIntegrityException in relation with SNS.

The original issue was caused by the fact that SNS location changes are performed directly against the cached nodes, in the transient session, while the query matches location from the indexes against the transient locations, causing invalid nodes to be returned by the query results.

The fix was to make the query results locate the node by the UUID first (if such information is available) and only as a fallback, use the location directly.

    • -0
    • +14
    ./src/test/resources/memory/nodetypes.cnd
  1. … 6 more files in changeset.
MODE-1450- Disabled check-in checks when importing xml content

    • -0
    • +191
    ./src/test/resources/io/drools/guvnor-empty-repository.xml
  1. … 1 more file in changeset.
MODE-1450- Disabled check-in checks when importing xml content

    • -0
    • +191
    ./src/test/resources/io/drools/guvnor-empty-repository.xml
  1. … 1 more file in changeset.
Released ModeShape 3.0.0.Alpha3

  1. … 45 more files in changeset.
MODE-1389 - Updated assemblies and descriptors

  1. … 38 more files in changeset.
MODE-1424 Fixed indexing deadlocking

There are two important changes involved: the locking around Lucene's IndexWriter has been made reentrant while the composite requests created by the indexer have been made read-only

    • -0
    • +1
    ./src/test/resources/federated/redhatMixin.cnd
  1. … 6 more files in changeset.
MODE-1424 Fixed indexing deadlocking

There are two important changes involved: the locking around Lucene's IndexWriter has been made reentrant while the composite requests created by the indexer have been made read-only

    • -0
    • +1
    ./src/test/resources/federated/redhatMixin.cnd
  1. … 6 more files in changeset.
MODE-1421 Fixed search schema data for sessions

Also, cleaned up some duplication in a pom file

  1. … 3 more files in changeset.
MODE-1421 Fixed search schema data for sessions

Also, cleaned up some duplication in a pom file

  1. … 3 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.
Release: update versions for modeshape-3.0.0.Alpha1

  1. … 45 more files in changeset.