Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Changes some of the webapps DOCTYPE to use XML namespacing. The reason is that with the old DOCTYPE style Jetty may fail when the running computer is not connected to the internet.

  1. … 4 more files in changeset.
Changes some of the webapps DOCTYPE to use XML namespacing. The reason is that with the old DOCTYPE style Jetty may fail when the running computer is not connected to the internet.

  1. … 4 more files in changeset.
MODE-2528, MODE-2558 Integrates the new relational provider with the Wildfly kit Also, it fixes some of the SchematicDB caching and locking logic, to avoid certain cases when data read before locking could be stale and therefore cause overall corruption by overwriting previous updates.

  1. … 81 more files in changeset.
MODE-2242 Added back 'modeshape-security' security domain, though it now uses existing 'ApplicationRealm' to manage users/roles

Changed back to a "modeshape-security" security domain that reuses the existing "ApplicationRealm" security realm for authentication. So users with ModeShape roles are still added via the EAP add-user.sh script (resulting in encrypted passwords).

  1. … 22 more files in changeset.
MODE-2242 Added back 'modeshape-security' security domain, though it now uses existing 'ApplicationRealm' to manage users/roles

Changed back to a "{{modeshape-security}}" security domain that reuses the existing "{{ApplicationRealm}}" security realm for authentication. So users with ModeShape roles are still added via the Wildfly (and EAP) {{add-user.sh}} script (resulting in encrypted passwords).

  1. … 21 more files in changeset.
MODE-2242 Changed the default security domain to "other" and adapted the existing tests to overwrite the default, still allowing the use of the modeshape-users and modeshape-roles properties files.

  1. … 41 more files in changeset.
MODE-2242 Removed the ModeShape security domain and chaged the WF kit to use by default the "other" security domain and hence the ApplicationRealm.

  1. … 36 more files in changeset.
MODE-2081 Changed the license for ModeShape code to ASL 2.0.

  1. … 559 more files in changeset.
MODE-1944 Migrated ModeShape EAP kit to EAP 6.1.0.GA. This presented a number of challenges: - RestEASY 2.3.6 excludes explicity a dependency required by resteasy-multipart-provider/apache.james. For this to work, it had to be re-added with the scope "runtime" - Deploying exploded webapps does not work anymore (for whatever reason...). This means that our EAP kit had to be changed to provide packaged .war files for the web application. This brought forth several issues around the subsystem and the content of the wars which was fixed.

    • -0
    • +9
    ./jboss-deployment-structure.xml
  1. … 20 more files in changeset.
MODE-1662 - Cleaned up the "connect" role, updating the documentation in the web.xml files where it's being used and removing any internal usages

  1. … 8 more files 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

  1. … 624 more files in changeset.
MODE-1439 Added new JndiRepositoryFactory implementation in ModeShape's API

Added a new JNDI-based RepositoryFactory that looks for only "jndi:"-type URLs, and is

aware of both Repository instances and (ModeShape-specific) Repositories instances.

This allowed simplification of the web library used in the RESTful and WebDAV services,

since they only need to specify the normal RepositoryFactory parameters in the

web.xml.

All unit and integration tests pass.

  1. … 32 more files in changeset.
MODE-1430: Changes to allow the REST war to deploy to AS 7. Updated the security name and added module dependencies to the manifest.

  1. … 1 more file in changeset.
MODE-813 - kit rearrangement. The new kit is called modeshape-jbossas-dist.zip. The new context are: modeshape-rest and modeshape-webdav.

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2060 76366958-4244-0410-ad5e-bbfabb93f86b

  1. … 12 more files in changeset.
MODE-813 - renamed resources-madeshape.war to resources-modeshape-rest.war, so that the webdav war (resources-modeshape-webdav.war) and the rest war can be disquishable. Also, fixed a change to the org.modeshape.deploy dependency that was incorrect in the kit.xml.

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2041 76366958-4244-0410-ad5e-bbfabb93f86b

  1. … 1 more file in changeset.
MODE-814 - changed to support the JNDI url of jndi:{jndiName} (without the 2 forward slashes as before).

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2023 76366958-4244-0410-ad5e-bbfabb93f86b

  1. … 4 more files in changeset.
MODE-814 - added a web.xml test resource that will be used (overlayed) for testing, and the main web.xml is the one used for jboss deployment that's configured to lookup its repositories via JNDI.

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2017 76366958-4244-0410-ad5e-bbfabb93f86b

  1. … 2 more files in changeset.
MODE-813 Changed the mbean deployment to pass a URL to the ManagedEngine at boot time

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@1985 76366958-4244-0410-ad5e-bbfabb93f86b

MODE-805 Renamed the projects under the 'deploy/jbossas' folder to match the pattern used for other projects.

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@1959 76366958-4244-0410-ad5e-bbfabb93f86b

  1. … 25 more files in changeset.