1 of 1 people found this helpful
Although you said you're running EAP 6.1.x and ModeShape 3.6.0, you've not stated whether you're running the ModeShape subsystem for EAP or embedding ModeShape in your application(s).
If the latter, have a look at our documentation for the repository deploy/undeploy methods on the ModeShapeEngine.
If using the ModeShape subsystem, you'll use the command line interface (CLI) or remote admin API to interface with the subsystem. Again, look at our documentation for details on how to reload the ModeShape subsystem.
many thanks for the hint.
I am running the Modeshape subsystem for EAP. I just tested the reload command of the Command line interface and it worked fine for me. Actually not just the Modeshape subsystem but all other subsystems are reloaded using the following command:
$JBOSS_HOME/bin/jboss-cli.sh --connect --command="reload"
I could not find a way to start just the modeshape subsystem.
The CLI is pretty powerful, and you can do lots of things in various places. For example, while at the top, you should be able to do this:
[standalone@localhost:9999 /] ./subsystem=modeshape/repository=sample:reload
or, you can navigate from the root into the repository and reload from there ...
[standalone@localhost:9999 /] cd /subsystem=modeshape/repository=sample
[standalone@localhost:9999 /subsystem=modeshape/repository=sample] :reload
1. When entering ":" and pressing the tab key below the list of available properties
[standalone@localhost:9999 subsystem=modeshape] : add read-children-resources read-operation-names remove write-attribute read-attribute read-children-types read-resource undefine-attribute read-children-names read-operation-description read-resource-description whoami
The "reload" property is not part of it showing that i can use it specific for this subsystem as for example the "add" property
2. when just the pressing the tab key below the list of available properties
[standalone@localhost:9999 subsystem=modeshape] alias connect echo-dmr ls read-operation undeploy batch data-source help module reload version cd deploy history pwd run-batch xa-data-source clear deployment-info if quit shutdown : command deployment-overlay jdbc-driver-info read-attribute try
The "reload" property is now available in the list of global properties which always apply to the whole server. This explains why all subsystems are reloaded for me
I am just wondering why the ":reload" command is working for you. Which version of JBoss are you using?
May be i am missing some configurations. I am using JBoss Enterprise Application Platform - Version 6.1.0.GA