{"shas":[["b45b563e70e059135e417a39ca8c6284e6e6b691","235015caf9d8148df6b3b4f79567dab7b3ba46e8@redhat.com","MODE-1164 Change configuration to use JDBC data source rather in-memory.\n\nHSQL will be used because it is the default database/datasource used in JBoss AS","Van Halbert"],["014683dce603b65ba8c5e80eb1eb1170f7e6b0cf","235015caf9d8148df6b3b4f79567dab7b3ba46e8@redhat.com","Mode-1230 added disk connector to the jboss kit","Van Halbert"],["85c41db8cfd0ffe52289ed1b98285412b8e80c6c","735b89142a149829186578b6196295ee17d089c2@redhat.com","MODE-1227 Added documentation for ModeShape RHQ plugin\n\nAdded a new chapter in the Reference Guide that describes the ModeShape RHQ plugin.","Ted Jones"],["652459026def210498e3f3c8bb728c605cecd0b8","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1224 Improve startup time of Repository\n\nSeveral changes were made to improve the startup time of the ModeShape engine and Repository instances, especially when starting up after the first shutdown.\n\nThe JPA connector was improved to eliminate a dual-connection startup mode that attempted to discover the model before establishing the actual connection. This will have a noticeable impact when starting up with 'autoGenerateSchema' properties of 'update' or 'validate', since before this change both connection phases performed the update and/or validation. Now that there is only a single connection phase, the update and/or validation will only be performed once.\n\nThis change also improves the process of reading the existing node types during JcrRepository startup. Prior to this change, the existing node types were read from the '/jcr:system' area and the built-ins were always loaded from a CND on the classpath, replacing any \"incorrect\" or \"invalid\" built-in node type that was stored in '/jcr:system'. Now, the existing node types are read from the '/jcr:system' area and used as is, without overwriting the built-ins. This was thought to better accept any existing node types configured by the user, and will perhaps come into play when a user upgrades from 2.x to 3.x (assuming there are changes to the built-ins). As a result, users will be responsible for updating the built-in node types using the standard NodeTypeManager.registerNodeTypes(…) methods.\n\nSeveral automated and manual integration tests were modified before these changes to allow better measurement of the startup times. Some test utility methods (e.g., simulation of Guvnor activities) were refactored so they could be more easily used in multiple (kinds of) tests.\n\nAll unit and integration tests pass with these changes, and a full build (e.g., \"mvn install -Pintegration\") appears to take 1 minute less.","Randall Hauch"],["1eaf46e51578f38c568716b65130b5f0fe2660a7","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","Miscellaneous fixes to a test class and rearranging the cache refreshing logic.","Randall Hauch"],["d902fcfe8764835f29d138a242006891fa73569c","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1232 Add support for REFERENCE nodes to FS connector\n\nAdded support in the file system connector for handling 'mix:referenceable' nodes and correctly handling the 'jcr:uuid' property. The connector still does not handle finding nodes by identifier (e.g., UUID).\n\nAlso changed the JcrSession (and associated classes) to better handle looking up nodes by identifier if the connector doesn't support doing so. In such cases, the JcrSession performs a query to search for the path of the node given the UUID, and then looks up the node by path. Note that when the referenceable nodes are still in the session's transient state, the session is now able to find them without resorting to the connector or queries.\n\nA new integration test case was added to test for this functionality. Prior to the above fixes, this test case failed (as expected); after the above fixes, the test case passes.\n\nAll unit and integration tests pass.","Randall Hauch"],["111c31ac916806246f641c52c360fd447b960344","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1221 Added test case to verify bug doesn't exist.","Randall Hauch"],["b622706ded3f08b5d254241e8b5fc556da34050d","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1221 Removed print statement","Randall Hauch"],["51a2348562927cedcb0a15358937738ac31962ae","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","Updated release notes","Randall Hauch"],["2f894a5c3bdcad13b8477eb591dbf48c17314346","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1234 Corrected indexing and querying of BOOLEAN properties\n\nQuery nodes based upon custom node types with BOOLEAN properties did work, whereas querying nodes based upon built-in node types with BOOLEAN properties did not work. This fix corrects one error in the way properties are indexed, and another in how constraints against BOOLEAN properties are transformed into Lucene queries. These two errors cancelled each other out for properties on custom node types, but caused issues with properties on built-ins.\n\nOnce this fix is applied (through an upgrade to 2.6.0.Final, the indexes should be rebuilt to correct the existing indexes.\n\nAll unit and integration tests pass, including several new tests written to duplicate/verify the problem.","Randall Hauch"],["ecaba59cc04c209a55865ca9cf1933568211dedb","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","Corrected description in Reference Guide.","Randall Hauch"],["b0f2cdc9df9bd214a2dd2aab6b2d83fec7d4c651","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1236 Added INFO-level log messages for reindexing\n\nChanged the existing log messages used during the beginning and end of the reindexing process from debug-level to info-level, and adjusted the messages to include the repository name (and workspace name if an entire workspace is being reindexed).\n\nAll unit and integration tests pass.","Randall Hauch"],["1d76ec20d2e838a92c3aadeb5fa9f20c102c2cda","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1237 Corrected handling of empty results from subquery.\n\nCorrected how the query execution handles putting the subquery results into the variables, so that even\nan empty array of tuples is put into the variables. Without this, when executing and using the subquery results,\nthe execution logic gets a null for the subquery 'variable' and records an error rather than just using an empty\narray.\n\nAll unit and integration tests pass with these changes.","Randall Hauch"],["cb674f1c96fdbc8150ad518922b122adcde61a0a","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","Slightly improved the query examples section.","Randall Hauch"],["d4422a35598c78130b16e6e1c963a5d9fa6c9346","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","Corrected DocBook error in query examples section.","Randall Hauch"],["6d265ae7de80429f44d156103ad5d9f06fff51fa","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-931 Corrected offset projection behavior\n\nChanged the logic in the JoinRequestProcessor to correctly handle offset projections (along with other projections)\nwhen processing ReadNodeRequests.\n\nA new integration test was added, and all unit and integration tests pass with these changes.","Randall Hauch"],["b186cf83daf45ac67032326756d9870ffd6b0152","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1150 Upgraded to SLF4J 1.6.1\n\nChanged the SLF4J dependency from 1.5.11 to 1.6.1, including all of the documentation and the various web and jboss related modules.\n\nNote that 1.6.x has changed its API slightly, and this breaks some libraries. Therefore, 1.6.x has to be used for all SLF4J-related libraries; one critical issue proved to be the \"org.slf4j:jcl-over-slf4j\" artifact that apparently is no longer needed (or at least needs to be the same version, and because RESTEasy had an explicit dependency on the then there was some work in excluding it from the web- and jboss- related ModeShape modules.\n\nAll unit and integration tests pass with these changes.","Randall Hauch"],["a0df9648e4420df501a17f4e8496c7e264634efc","3611b7acafbd61e94d2c92d3bf5b450e9781ef8b@soluvas.com","Upgrade Logback to 0.9.29 in Examples","Hendy Irawan"],["cb2880391c4c63c9d49e50ee2e2bfd3402e40d29","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1241 Corrected duplicate serialization of properties in JPA source\n\nThe JPA source was handling UpdatePropertyRequests by iterating through its properties and then removing or\nupdating the property on the JPA node. Each time a property was modified (removed or added or updated), all\nof the nodes properties were serialized. This not only is WAY more work than needed, but it causes a\nproblem when a file backed Binary value is used (since the first serialization closes the backing stream,\nand subsequent serialization attempts to use the closed stream).\n\nThis was fixed by simply changing how the UpdatePropertyRequests are handled in MapRequestProcessor to\nupdate and remove all of the appropriate properties in one shot, via a modified 'setProperties' method on\nthe MapNode, DefaultMapNode, and JpaNode. Because the MapNode interface was changed, several other uses\nrequired modification.\n\nVan's test case was able to duplicate the problem prior to these changes. After these changes, all\nunit and integration tests pass.","Randall Hauch"],["cbc3df265df15c2e49f67350b1bc399a3e6ea93e","9972a9c98f4ad2f4c07879e61ff8ef543017832b@gmail.com","MODE-1242 RepositoryFactory should support JNDI URL to Repository instance\n\nThe JcrRepositoryFactory implementation should support JNDI URLs that point to a Repository instance rather than a ModeShape engine.\n\nWhen deploying ModeShape to Glassfish or Tomcat, using JndiRepositoryFactory will often be used to register specific Repository instances in JNDI, making the JCR-2.0-style lookup impossible without this change.\n\nAll unit and integration tests pass with this change.","Randall Hauch"]],"ref":"refs/heads/master","size":25,"head":"3361247f3f6d535d01e92d2ad5549f48c37859b0","push_id":40566677}