Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: modeshape-3.0.…
Commits on Mar 28, 2012
  1. @rhauch

    Released ModeShape 3.0.0.Alpha3

    rhauch authored
Commits on Mar 26, 2012
  1. @hchiorean
Commits on Mar 23, 2012
  1. MODE-1441: Added ModeShape schema to docs/schema folder of AS 7 kit. …

    Ted Jones authored
    …Renamed the file to modeshape_3_0.xsd to conform with the other schema names in that folder.
  2. @hchiorean
  3. @hchiorean
Commits on Mar 22, 2012
  1. @rhauch

    MODE-1439 More changes to get AS 7 kit working

    rhauch authored
    Additional changes to support running the ModeShape subsystem within AS 7. There still are
    some issues, but they will be addressed with MODE-1435 and MODE-1437.
  2. @rhauch

    MODE-1439 Added new JndiRepositoryFactory implementation in ModeShape…

    rhauch authored
    …'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
    All unit and integration tests pass.
  3. @rhauch

    Merge branch 'MODE-1392' of in…

    rhauch authored
    …to hchiorean-MODE-1392
  4. MODE-1430: Changes to allow the REST war to deploy to AS 7. Updated t…

    Ted Jones authored
    …he security name and added module dependencies to the manifest.
  5. @hchiorean
  6. @hchiorean

    MODE-1392 Extended the JCR event model with an additional sequencing …

    hchiorean authored
    …event. Updated sequencing unit tests to make use of this event.
Commits on Mar 21, 2012
  1. MODE-1412: Added security domain for modeshape

    Ted Jones authored
  2. @rhauch

    MODE-1405 Corrected how JCR import handles protected content

    rhauch authored
    Corrected the behavior of the JCR import logic to always import protected content.
    The whole point of importing a previously-exported file is to recover all of the
    content the way it was, including the 'jcr:created', 'jcr:createdBy' and other
    protected properties. (Although note that the 'jcr:lastModified' and 'jcr:lastModifiedBy'
    properties will still be updated during the import.)
    Added a new unit test to verify that the import now works correctly with protected content.
  3. @rhauch

    MODE-1434 Added support for discovering JDBC drivers with Java servic…

    rhauch authored
    …e provider mechanism
    A 'META-INF/services/java.sql.Driver' file was added to each of our JDBC driver implementations, and the JAR files
    were verified to contain these new files.
  4. @rhauch

    MODE-1430 Additions/corrections to the JBoss AS7 kit

    rhauch authored
    The sequencer module names were changed to start with 'org.modeshape' rather than just 'modeshape'.
    Also added a module for the local JDBC driver.
  5. @rhauch

    MODE-1430 Changes to the AS7 kit to automatically deploy the RESTful WAR

    rhauch authored
    A few changes were made to include a 'modeshape-rest.war.dodeploy' marker file
    in the 'standalone/deployments' directory. This file is not needed when
    automatic detection is enabled (which is the default), but it is needed when
    automatic detection has been disabled prior to installing the ModeShape kit.
  6. @rhauch

    MODE-1430 Enabled the RESTful services within the build

    rhauch authored
    The Maven modules that make up the RESTful service and it's dependencies (e.g., the
    local JDBC driver) have been added back into the build. Several changes were required
    to correct the test cases' expected results, and to change the test repository
    configurations. The JBoss AS 7 kit also is now including the customized RESTful
    WAR file.
Commits on Mar 20, 2012
  1. @rhauch

    MODE-1383: Bound the ModeShape engine to JNDI using jcr/local

    Ted Jones authored rhauch committed
Commits on Mar 18, 2012
  1. MODE-1412: Upgaded subsystem to JBossAS 7.1.1.Final

    Ted Jones authored
Commits on Mar 16, 2012
  1. @rhauch

    MODE-1425 Upgraded JodaTime to 1.6.2

    rhauch authored
    JBoss AS 7.1.1.Final uses JodaTime 1.6.2, so this library was upgraded to match this
    (from 1.6).
  2. @rhauch

    MODE-1379 MODE-1426 1427 Upgraded Infinispan, JGroups and PicketBox

    rhauch authored
    The dependency on Infinispan was upgraded to 5.1.2.FINAL, which is the same version used by
    JBoss AS 7.1.1.Final. The JGroups version was also changed to match that used by Infinispan
    5.1.2.FINAL (and JBoss AS 7.1.1.Final). Also, the PicketBox version was upgraded to the
    same version used in JBoss AS 7.1.1.Final.
    The Infinispan upgrade required some changes to how the DeltaAware-related code works, since
    that framework was changed between 5.1.0.BETA3 and 5.1.0.FINAL (though this was unchanged
    since then).
    All current unit and integration tests pass.
  3. @rhauch

    MODE-1428 Upgraded RESTEasy

    rhauch authored
    RESTEasy was upgraded to the same version used within JBoss AS 7.1.1.Final. An additional
    dependency on 'jboss-common-core' was needed for tests in the 'modeshape-jcr' module, since
    it is no longer exposed by RESTEasy.
  4. @rhauch

    MODE-1423 SchematicEntryLiteral annotated with Externalizer class

    rhauch authored
    The Externalizer for the SchematicEntryLiteral class is an AdvancedExternalizer, but
    this requires proper configuration (in Infinispan XML or programmatic config) for it to
    work. This change adds the '@SerializedWith(...)' annotation to the SchematicEntryLiteral
    class to specify the Externalizer implementation, which means the annotation-based
    ClassExternalizerFactory should find it.
Commits on Mar 12, 2012
  1. @rhauch

    MODE-1418 Corrected certain queries with full-text search criteria

    rhauch authored
    Certain JCR-SQL2 full-text search criteria were not being processed correctly.
    Any f.t.s. criteria that specified a single property resulted in an incorrect
    query plan.
    Several changes were made to correct this behavior, and new unit tests were added.
  2. @rhauch

    MODE-1420 Fixed unwanted Hibernate Search warning messages

    rhauch authored
    Hibernate Search's SearchConfiguration class defines a "isTransactionManagerExpected()"
    method that dictates whether the warning messages should be logged (and that appears
    to be the only way in which this method is used).
    So far, ModeShape's org.modeshape.jcr.query.lucene.LuceneSearchConfiguration implementation
    has returned 'true'. But this method should return 'false', since the re-indexing operations
    are not performed within a transaction, so Hibernate Search shouldn't always expect a
    transaction. Simply making this change makes the problematic log messages disappear, but
    doesn't otherwise affect any functionality.
    All unit and integration tests pass with these changes.
  3. @rhauch

    MODE-1365 Added more support for queries

    rhauch authored
    Lots of changes in the portions of the ModeShape code that's using Lucene, including the
    general interfaces and reusable queries (in org.modeshape.jcr.query.lucene) and the basic
    schema that uses a single index (in org.modeshape.jcr.query.lucene.basic).
    At this point, all query functionality appears to work except for full-text search.
    All current tests pass with these changes, though more testing is required.
  4. @hchiorean
  5. @hchiorean
  6. @rhauch

    MODE-1417 Corrected versioning of files uploaded through REST client

    rhauch authored
    The REST client library was versioning only the 'jcr:content' child node of an
    'nt:file' node. While that's acceptable (since it's where the file's content is
    actually stored), it's better if the 'nt:file' node itself was versioned.
    This change simply changes the node where the 'mix:versionable' mixin is applied.
    When a new 'nt:file' node is uploaded, that node is now made versionable instead
    of the 'jcr:content' child. All existing content is still handled and versioned
    correctly (as it was), and this change only affects content added using a
    RESTful client that contains the fix.
    This change only affects the RESTful client, which is never used within the
    server-side installation of ModeShape.
    All unit and integration tests pass with these changes.
Commits on Mar 8, 2012
  1. @tejones @rhauch

    MODE-1319: Cleaning up code in service classes

    tejones authored rhauch committed
  2. @tejones @rhauch

    MODE-1319a: Added Sequencers

    tejones authored rhauch committed
Commits on Mar 6, 2012
  1. @hchiorean
Something went wrong with that request. Please try again.