In eXo Platform Tomcat, the Dev mode is turned on by appending
--dev to the startup command: ./start_eXo.sh --dev.
This parameter will add the following system properties:
In eXo Platform JBoss, the
--dev parameter is not supported.
You need to customize environment variables to have the following variable:
Effects of Dev mode
Hereafter are effects of the Dev mode:
Magic locale - A language option called magic locale - with the code ma - is added. It is useful for debugging localization resource. In this language, all labels are displayed as the resource name instead of the translated values:
INFO | Add configuration jar:file:/media/data/doc/3295/test/platform-4.0.5/lib/exo.kernel.component.common-2.4.8-GA.jar!/conf/portal/generic-configuration.xml [e.k.container.ConfigurationManagerImpl<Catalina-startStop-1>] INFO | Add configuration jndi:/localhost/portal/WEB-INF/conf/configuration.xml [e.k.container.ConfigurationManagerImpl<Catalina-startStop-1>] INFO | import jndi:/localhost/portal/WEB-INF/conf/common/common-configuration.xml [e.k.container.ConfigurationManagerImpl<Catalina-startStop-1>] INFO | import jndi:/localhost/portal/WEB-INF/conf/common/resource-compressor-configuration.xml [e.k.container.ConfigurationManagerImpl<Catalina-startStop-1>]
Moreover, the Dev mode allows the hot re-loading of configuration. You can modify container configuration without restarting the server. The hot re-loading can be done via JMX clients, such as JConsole, as follows:
Connect JConsole to the eXo Platform process.
Find an MBean with object name:
See more details in eXo Kernel reference.
Unpacking .war files (Tomcat) -
Particularly to eXo Platform Tomcat in the Dev mode, the startup scripts also set
that results in decompressing .war archives in webapps folder.