Hide Forgot
securitylevel_name: Public When starting the server, when ModeShape is used as the repo, the following error is seen in the log: 2011-06-29 12:48:32,553 ERROR [org.modeshape.jcr.RepositoryNodeTypeManager] (modeshape-start-repo-2-thread-1) Node types were read from the system content, and appear to be inconsistent or invalid: org.modeshape.jcr.nodetype.InvalidNodeTypeDefinitionException: Supertype 'nt:hierarchyNode' from type 'drools:configurationNodeType' does not exist Restarted server after deleting the default/data/modeshape directory, and still see the error.
Can you attached the modeshape configuration, if its been changed from the default.
Can you please include a link to the configuration file?
Default delivered configuration.
Attachment: Added: modeshape-config.xml
ModeShape brms hsql datasource file
Attachment: Added: modeshape-brms-store-ds.xml
Link: Added: This issue Cloned to BRMS-634
I've written a unit test in ModeShape's codebase that: # starts a new engine (using a disk-based JPA source), # loads the Drools node types, # gets all of the available node types (which would include the built-ins plus the Drools node types) # shuts down the engine # starts up a new engine (using the same disk-based JPA source), # gets all of the available node types (which would include the built-ins plus the Drools node types) # compares the node types from step 3 and step 6, making sure that the node types match I cannot get the test case to fail. Furthermore, based upon the information in this defect, we should be getting an error in step 5, and we are not. It's strange that the error message reports that the 'nt:hierarchyNode' cannot be found, because that is a built-in node that is always available. This error makes no sense to me at all.
Try to replicate by running within JBoss AS 5.1. Changed modeshape-config.xml to add the drools related .cnd files Tried the order that BRMS uses: <mode:resource>configuration_node_type.cnd</mode:resource> <mode:resource>tag_node_type.cnd</mode:resource> <mode:resource>state_node_type.cnd</mode:resource> <mode:resource>versionable_node_type.cnd</mode:resource> <mode:resource>versionable_asset_folder_node_type.cnd</mode:resource> <mode:resource>rule_node_type.cnd</mode:resource> <mode:resource>rulepackage_node_type.cnd</mode:resource> and tried the order that modeshape using in integration tests: <mode:resource>versionable_node_type.cnd</mode:resource> <mode:resource>versionable_asset_folder_node_type.cnd</mode:resource> <mode:resource>rule_node_type.cnd</mode:resource> <mode:resource>rulepackage_node_type.cnd</mode:resource> <mode:resource>state_node_type.cnd</mode:resource> <mode:resource>tag_node_type.cnd</mode:resource> <mode:resource>configuration_node_type.cnd</mode:resource> and neither produced the error. Going to replace the modeshape in BRMS with the version I used to see if the issue still occurs.