modeshape-integration-tests

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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

    • -1447
    • +0
    ./src/test/byteman/jcr-performance.txt
  1. … 379 more files in changeset.
Updated POMs for next SNAPSHOT version

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

  1. … 62 more files in changeset.
Changed the version to 3.1.3-SNAPSHOT

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

  1. … 62 more files in changeset.
Updated version to 3.1.2-SNAPSHOT

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

  1. … 62 more files in changeset.
Changed versions to 3.1.1-SNAPSHOT for development

  1. … 61 more files in changeset.
Changed version number to 3.2-SNAPSHOT

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

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

  1. … 55 more files in changeset.
Changed POM versions to '3.1-SNAPSHOT'

  1. … 55 more files in changeset.
Changed POM version to '3.0.1-SNAPSHOT'

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

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

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

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

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

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

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

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

  1. … 48 more files in changeset.
MODE-1527 - Updated the text extraction process to be asynchronous with the indexing process.

This meant that a few changes were needed:

- the text extractors configuration has been updated to resemble that of the sequencers

- the binary store interface has been updated to be able to store and retrieve extracted text for a given binary (source) value

- the TextExtractors class was changed to become the entry point into text extraction

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

  1. … 47 more files in changeset.
MODE-1537 Corrected how manual transactions are implemented

ModeShape's initial support for JTA transactions included a bug that allowed this

only to work for the first transaction. The state of that first transaction was kept,

so ModeShape never registered a Synchronization implementation for subsequent transactions.

Although the data was correctly persisted as part of these transactions, none of the

events for the subsequent transactions were fired and thus the local caches became

out of date and failed to expose the newly added/modified/deleted content.

ModeShape's internal transaction abstraction was corrected and simplified so that

the transactional state is never managed by the system but instead is referenced

by the client code using the transactions. This does make the API slightly more complex,

but it greatly simplifies the implementation and corrects the transactional behavior.

A new integration test was added to use a SLSB with BMT to create a subgraph of nodes

in one (or more) transactions, verify the structure (using a different transaction),

and remove the subgraph in another transaction.

All unit and integration tests pass with these changes.

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

  1. … 47 more files in changeset.
Corrected parent POM reference from JBoss AS integration tests

  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

    • -0
    • +0
    ./src/test/byteman/jcr-performance.txt
  1. … 610 more files in changeset.