[ https://jira.jboss.org/jira/browse/DNA-340?page=com.atlassian.jira.plugin... ] Randall Hauch commented on DNA-340: ----------------------------------- Applied the patch, which stores the node type information in the repository graph, with one exception. For various reasons (including those related to performance of running so many TCK unit tests), we want to be able to have a JcrRepository configuration property that says whether the node types should be stored in the graph. So, the "batch.execute()" line was commented out at the end of the RepositoryNodeTypeManager.projectOnto(Graph,Path) method. This essentially prevents the node types from being added, but still ensures that the "/jcr:system/dna:nodeTypes" node exists. Leaving this issue open until the configuration option is addressed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-340?page=com.atlassian.jira.plugin... ] Randall Hauch commented on DNA-340: ----------------------------------- Applied the 2nd patch, which adds support to JcrRepository for configurable options, with a single option as to whether or not the node types should be projected under "/jcr:system/dna:nodeTypes". Minor change from the patch was to reorder the constructor parameters of JcrRepository to match the other existing constructor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira