Permalink
Switch branches/tags
modeshape-5.4.1.Final modeshape-5.4.0.Final modeshape-5.3.0.Final modeshape-5.2.0.Final modeshape-5.1.0.Final modeshape-5.0.0.Final modeshape-4.6.2.Final modeshape-4.6.1.Final modeshape-4.6.0.Final modeshape-4.5.0.Final modeshape-4.4.0.Final modeshape-4.3.0.Final modeshape-4.2.0.Final modeshape-4.1.0.Final modeshape-4.0.0.Final modeshape-4.0.0.Beta2 modeshape-4.0.0.Beta1 modeshape-4.0.0.Alpha4 modeshape-4.0.0.Alpha3 modeshape-4.0.0.Alpha2 modeshape-4.0.0.Alpha1 modeshape-3.8.1.Final modeshape-3.8.0.Final modeshape-3.7.4.Final modeshape-3.7.3.Final modeshape-3.7.2.Final modeshape-3.7.1.Final modeshape-3.7.0.Final modeshape-3.6.1.Final modeshape-3.6.0.Final modeshape-3.5.0.Final modeshape-3.4.0.Final modeshape-3.3.0.Final modeshape-3.2.0.Final modeshape-3.1.3.Final modeshape-3.1.2.Final modeshape-3.1.1.Final modeshape-3.1.0.Final modeshape-3.0.1.Final modeshape-3.0.0.Final modeshape-3.0.0.CR3 modeshape-3.0.0.CR2 modeshape-3.0.0.CR1 modeshape-3.0.0.Beta4 modeshape-3.0.0.Beta3 modeshape-3.0.0.Beta2 modeshape-3.0.0.Beta1 modeshape-3.0.0.Alpha6 modeshape-3.0.0.Alpha5 modeshape-3.0.0.Alpha4 modeshape-3.0.0.Alpha3 modeshape-3.0.0.Alpha2 modeshape-3.0.0.Alpha1 modeshape-2.8.3.Final modeshape-2.8.2.Final modeshape-2.8.1.GA modeshape-2.8.1.Final modeshape-2.8.0.Final modeshape-2.7.0.Final modeshape-2.6.0.Final modeshape-2.6.0.Beta2 modeshape-2.6.0.Beta1 modeshape-2.5.0.Final modeshape-2.5.0.Beta2 modeshape-2.5.0.Beta1 modeshape-2.4.0.Final modeshape-2.3.0.Final modeshape-2.2.0.Final modeshape-2.1.0.Final modeshape-2.0.0.Final modeshape-1.2.0.Final modeshape-1.1.0.Final modeshape-1.0.0.Final modeshape-1.0.0.Beta1 dna-0.7 dna-0.6 dna-0.5 dna-0.4 dna-0.3 dna-0.2 dna-0.1 EDS_5.3.1_2_2014 3.8.x-prod-ip6.1-ER1
Nothing to show
Commits on Jan 14, 2011
  1. [maven-release-plugin] copy for tag modeshape-2.4.0.Final

    Randall Hauch committed Jan 14, 2011
    git-svn-id: https://svn.jboss.org/repos/modeshape/tags/modeshape-2.4.0.Final@2670 76366958-4244-0410-ad5e-bbfabb93f86b
  2. MODE-1066, MODE-1071 Added a new background garbage collection facili…

    Randall Hauch committed Jan 14, 2011
    …ty to the connector API and ModeShape engine
    
    This new facility includes:
    - a new CollectGarbageRequest, with a field allowing the connector to specify whether the garbage collection
      operation was completed or whether another pass could/should be made by the requestor
    - a default implementation of the RequestProcessor.process(CollectGarbageRequest) that does nothing; existing
      connectors by default implement this behavior and don't need to change
    - a new field on RepositorySourceCapabilities that allows the connector to express whether it automatically
      cleans up unused content (collects garbage), or whether it needs to be done with an explicit CollectGarbageRequest
    - a new method on RepositoryService (which owns the library of RepositorySource instances) that will find the
      RepositorySource instances that require explicit garbage collection, and upon these (if there are any)
      iteratively make the CollectGarbageRequest; the source will be enqueued again if another collection pass is required
    - a new background scheduled executor in ModeShapeEngine (the superclass of JcrEngine) to periodically (and
      in a background thread) have the RepositoryService collect garbage on its sources.
    - a new configuration property that defines the time interval for the periodic, background garbage collection
      (the default is every 10 minutes).
    
    Also changed the JPA connector to override the RequestProcessor.process(CollectGarbageRequest) by removing all
    unused LargeValueEntity records in all workspaces, and to declare  in its RepositorySourceCapabilities that manual
    GC is required. Since this is now done explicitly, removing nodes no longer removes unused LargeValueEntity records.
    This should improve the performance of certain operations, and because the LargeValueEntity records (keyed by
    their SHA-1) stick around for a longer period of time, they remain available to be reused. For example, if repository
    content is removed but replaced with mostly similar content, any large values (strings or binary property values)
    that are the same actually would be reused.
    
    Also, the MySQL-specific logic for removing LargeValueEntity (see MODE-691) was changed to use a single native SQL
    delete statement. This is much more efficient, and on-par with the HQL delete statement used for other Hibernate
    dialects. The native MySQL statement was needed because HQL was inadequate for deleting the unused LargeValueEntity
    without resorting to a subquery that used the LargeValueEntity table, which is not supported by MySQL. So instead,
    the native MySQL delete statement uses a left outer join between the LargeValueEntity and "usages" table and a
    criteria on the result to ensure that the only records returned are those without any "usages" records in the
    tuples. This works because a left outer join between tables A and B always contains all records from A, whether
    or not there are no corresponding records from B. And, if a criteria is added such that a column from B that
    can never be null is actually null, then we know the result will contain only those records from A that
    do **not** have a corresponding B record. In our case, this ends up deleting only those LargeValueEntity records
    that are not referenced in the "usages" table (i.e., they are not used).
    
    Updated a couple of test cases and added a few more that deal with the new feature. A new "mysql5_local" database
    configuration was added to the POM, and this required modification of several test cases that depended on the
    database configuration name to find files in test data.
    
    All unit and integration tests pass while using HSQLDB and MySQL5.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2668 76366958-4244-0410-ad5e-bbfabb93f86b
  3. MODE-1066 Added several test cases to attempt to replicate the report…

    Randall Hauch committed Jan 14, 2011
    …ed problem (without success so far).
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2667 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Jan 13, 2011
  1. Correction to the logic in the JDBC driver's POM that removes duplica…

    Randall Hauch committed Jan 13, 2011
    …te files in the META-INF folder. Prior to this fix, the POM was hard-coded to use the 2.2.1 version.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2666 76366958-4244-0410-ad5e-bbfabb93f86b
  2. Corrected JDBC driver project's Maven version number.

    Randall Hauch committed Jan 13, 2011
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2665 76366958-4244-0410-ad5e-bbfabb93f86b
  3. Updated the Reference Guide and Getting Started Guide to reflect the …

    Randall Hauch committed Jan 13, 2011
    …2.4.0.Final version number and what's new in the 2.4.0.Final release.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2664 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Jan 11, 2011
  1. Added Van to the list of developers in the parent POM.

    Randall Hauch committed Jan 11, 2011
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2662 76366958-4244-0410-ad5e-bbfabb93f86b
  2. MODE-1027 Made one additional tweak: if the new content is considered…

    Randall Hauch committed Jan 11, 2011
    … 'mix:versionable', then the RESTful service will do a checkin (which is how the JCR API is used when content is newly marked as versionable).
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2659 76366958-4244-0410-ad5e-bbfabb93f86b
  3. MODE-1027 Improved the support for publishing versionable files.

    Randall Hauch committed Jan 11, 2011
    Changed the RESTful service to support modifying a subgraph via a PUT. With this change, the same JSON request for a POST (for create) could be sent as a PUT to update the subgraph rather than delete it. Of course, the JSON request only needs to include properties that change, although every child node needs to be specified. The previous PUT JSON request format (containing the properties to change) is still supported and behaves as before. Note that, before updating a node, the RESTful service first checks if the node is 'mix:versionable'. If it is, then the service checks out the node, modifies it, and then checks it back in. If it is not versionable, it just directly modifies the node.
    
    Also changed the REST client to no longer unpublish an existing file before publishing a new one. Instead, if the file is already there, it submits the new file as a PUT rather than a POST.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2658 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Jan 8, 2011
  1. MODE-1069 missing localization in the JDBC driver

    vhalbert committed Jan 8, 2011
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2657 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Jan 7, 2011
  1. Added test case that verified the behavior as brought up in a discuss…

    Randall Hauch committed Jan 7, 2011
    …ion thread.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2654 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Jan 6, 2011
  1. MODE-1067 Removed duplicate test and ignored another problematic test.

    Randall Hauch committed Jan 6, 2011
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2652 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Jan 5, 2011
  1. MODE-1066 Rolling back the correction of a unit test, since the Hudso…

    Randall Hauch committed Jan 5, 2011
    …n builds are failing with this change (though this change is required locally).
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2650 76366958-4244-0410-ad5e-bbfabb93f86b
  2. MODE-1067 The code contained three ways in which nodes were retrieved…

    Randall Hauch committed Jan 5, 2011
    … while processing the results of a query. One of these properly handled the case where the node was deleted in persistent storage, but was returned in the query result tuples because the indexes weren't yet updated to reflect the deletion. The two other ways were not handling this case, so these were corrected.
    
    All unit and integration tests pass with these changes.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2648 76366958-4244-0410-ad5e-bbfabb93f86b
  3. This is a fix to remove the duplicate files in the META-INF folder of…

    vhalbert committed Jan 5, 2011
    … the modeshape-jdbc-2.2.1-http-jar-with-dependencies.jar.   This will now enable the signing of the jar.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2647 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Jan 3, 2011
  1. MODE-997 - fix to the ResultSet date,time,timestamp methods that take…

    vhalbert committed Jan 3, 2011
    … a calendar as an argument, to better handle conversions from the internal calendar representation to the expected result based on the targeted calendar passed in.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2645 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Dec 23, 2010
  1. MODE-1049 Corrected four more unit tests that were failing due to rec…

    Randall Hauch committed Dec 23, 2010
    …ent changes with ISDESCENDANTNODE criteria.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2642 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Dec 22, 2010
  1. MODE-1049 Corrected one of the test cases (and added another) that de…

    Randall Hauch committed Dec 22, 2010
    …als with ISDESCENDANTNODE criteria. The expected results were incorrect.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2639 76366958-4244-0410-ad5e-bbfabb93f86b
  2. MODE-1052 Corrected the logic in the LuceneSearchEngine for handling …

    Randall Hauch committed Dec 22, 2010
    …NOT criteria.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2638 76366958-4244-0410-ad5e-bbfabb93f86b
  3. MODE-1049 Corrected the PlanUtil.replaceViewReferences(...) method, w…

    Randall Hauch committed Dec 22, 2010
    …hich was returning a ChildNodeJoinCondition when it should be returning a DescendantNodeJoinCondition instance. All unit and integration tests pass with this correction.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2636 76366958-4244-0410-ad5e-bbfabb93f86b
  4. MODE-1028 Corrected the JavaDoc for the JcrRepository.Option.VERSION_…

    Randall Hauch committed Dec 22, 2010
    …HISTORY_STRUCTURE, which incorrectly listed the default.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2634 76366958-4244-0410-ad5e-bbfabb93f86b
  5. MODE-1064 Updated the description of the JPA connector's "dialect" pr…

    Randall Hauch committed Dec 22, 2010
    …operty in the Reference Guide to now highlight the fact that auto-discovery of the dialect does not always work well on MySQL (especially with MySQL 5 InnoDB).
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2632 76366958-4244-0410-ad5e-bbfabb93f86b
  6. MODE-1028 Implemented this with a new internal graph 'net-change' obs…

    Randall Hauch committed Dec 22, 2010
    …erver on the JcrRepository instance. When the observer receives delete or move events, it queries the appropriate workspace for the 'mode:derived' nodes with a 'mode:derivedFrom' value that matches the path of the deleted or moved node(s) (using LIKE, as the deleted/moved nodes might be ancestors of the nodes pointed to by the 'mode:derivedFrom' value) and with a 'mode:derivedAt' timestamp that is on or before the delete/move event's timestamp (this ensures that the 'mode:derived' nodes were not added in a subsequent operation (e.g., the file is delete and then re-added).
    
    Note that 'mode:derivedAt' is a new DATE property that is now added by the StreamSequencerAdapter (the same code that adds the 'mode:derived' mixin.
    
    A new integration test was added to verify this new logic is performed correctly.
    
    Also, a JcrRepository.Option was added to control whether derived content should be removed. By default (when at least one sequencer is enabled), this new feature is enabled, meaning the repository will remove all content that was derived from other content being removed. However, if no sequencers are enabled, the default is to not enable this feature. Of course, the feature can be explicitly enabled or disabled by specifying the desired value for this option.
    
    Also added a new section to the Reference Guide that describes the JcrRepository.Option values.
    
    All unit and integration tests pass with these changes.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2629 76366958-4244-0410-ad5e-bbfabb93f86b
  7. MODE-1028 Corrected how PATH property values are indexed (they were i…

    Randall Hauch committed Dec 22, 2010
    …mproperly indexed as REFERENCE types).
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2628 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Dec 20, 2010
  1. Removed Oracle driver dependency from the 'modeshape-integration-test…

    Randall Hauch committed Dec 20, 2010
    …s' module, which was incorrectly added last week.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2627 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Dec 16, 2010
  1. MODE-1047 Corrected several of the JcrDriverIntegrationTests, which a…

    Randall Hauch committed Dec 16, 2010
    …pparently didn't specify the order of the results, allowing the query engine to return the results in any order. With this change, all unit and integration tests work.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2623 76366958-4244-0410-ad5e-bbfabb93f86b
  2. MODE-1047, MODE-1053 Changed the implementation of JcrWorkspace.copy(…

    Randall Hauch committed Dec 16, 2010
    …...) to query for 'mix:versionable' nodes in the source branch. The 'mix:versionable' nodes that result from the copying need to have their version histories initialized, and using a query simplifies the logic and is far more efficient as the ratio of versionable to non-versionable nodes decreases.
    
    This patch also has an implementation of the hierarchical structure for the version history nodes under '/jcr:system/jcr:versionStorage' (see MODE-1053). A new node type ('mode:versionHistoryFolder') was created to represent the intermediary folder nodes under 'jcr:versionStorage' but above the 'jcr:versionHistory' nodes. This additional node type required a change in the expected results of several tests.
    
    A new integration test was added to exercise the BRMS-like performance test, but because these tests take a while, they are marked @Ignore. To run locally, simply remove this annotation, recompile and run.
    
    All unit and integration tests still pass with these changes.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2622 76366958-4244-0410-ad5e-bbfabb93f86b
  3. Corrected more Maven issues, particularly with OS-specific resource c…

    Randall Hauch committed Dec 16, 2010
    …opies and duplicate dependencies.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2619 76366958-4244-0410-ad5e-bbfabb93f86b
  4. Fixed several minor Maven warnings or errors, including a duplicate d…

    Randall Hauch committed Dec 16, 2010
    …ependency, a version discrepancy with Google Collections, and an export package warnings with the OSGi bundling.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2618 76366958-4244-0410-ad5e-bbfabb93f86b
  5. MODE-1057 The RepositoryNodeTypeManager was not writing the PropertyD…

    Randall Hauch committed Dec 16, 2010
    …efinition.getAvailableQueryOperators() to the graph, so any query operators were not properly being persisted. This showed up in the ClusterTest when a new property definition with a specific operator was created in one process and loaded into the other processes in the cluster.
    
    The fix was to properly persist the query operators for each property definition. All unit and integration tests pass now.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2614 76366958-4244-0410-ad5e-bbfabb93f86b
  6. MODE-1057 Several components were changed to support using the Proper…

    Randall Hauch committed Dec 16, 2010
    …tyDefinition.getAvailableQueryOperators() and PropertyDefinition.isOrderable(). The schemata-related classes were changed to capture this information, and the NodeTypeSchemata class was changed to populate this information based upon the PropertyDefinition. The query validation logic was changed to check the schemata's column information for Comparison and Ordering objects.
    
    All unit and integration tests pass with these changes.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2611 76366958-4244-0410-ad5e-bbfabb93f86b
Commits on Dec 15, 2010
  1. MODE-1056 Added a check to NodeTypeSchemata that will not create a vi…

    Randall Hauch committed Dec 15, 2010
    …ew in the internal representation of queryable tables/views for a node definition that returns 'false' for 'isQueryable()'.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2609 76366958-4244-0410-ad5e-bbfabb93f86b
  2. MODE-1055 ModeShape does not need to enforce which properties can app…

    Randall Hauch committed Dec 15, 2010
    …ear within the SELECT, WHERE and ORDER BY clauses. Therefore, the JcrQueryManager class was changed to no longer validate the existence of columns during query validation. Several new unit tests were added to check the desired new behavior.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2607 76366958-4244-0410-ad5e-bbfabb93f86b
  3. Corrected Hibernate version to be that used by the JPA connector.

    Randall Hauch committed Dec 15, 2010
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2605 76366958-4244-0410-ad5e-bbfabb93f86b
  4. MODE-1054 The problem appears to be in the JPA connector, since the i…

    Randall Hauch committed Dec 15, 2010
    …n-memory connector works just fine. After adding several test cases, I think I've isolated the problem to the SimpleJpaRepository.getWorkspaceNames() method. This method is looking in its local cached state for the list of Workspaces, but each instance is owned by the SimpleJpaConnection object (which gets managed by the connection pool). Thus, when one request creates a new workspace using connection A and another request attempts to find the list of workspace names happens to get a different connection (e.g., connection B), this other connection's cached list of workspace names is out-of-sync with the store. This can be fixed by simply changing the SimpleJpaRepository.getWorkspaceNames() method to always read the names from the store.
    
    These changes include the new test cases, the 2-line fix to SimpleJpaRepository.getWorkspaceNames(), and a change to JcrRepository that caches the workspace names (although creating a session never uses this cache).
    
    With these changes, all unit and integration tests pass.
    
    git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2603 76366958-4244-0410-ad5e-bbfabb93f86b