Development vs Production mode in JOnAS ?

Development vs Production mode

JOnAS may be configured to be in development mode and in production mode. This can be defined by setting the jonas.development global property.

Development mode

This is the default mode.

Starts automatically the workcleaner (wc) service.

Allows to start automatically services which are required to initiate the deployment of the Java EE archives. Ex : deploying the sample.war will trigger the startup of the web service.

List of services that may be started dynamically depending on the deployed Java EE archives : 

web (WARs), ejb2 (EJB2s), ejb3 (EJB3s), resource (RARs), ear (EARs)

In case of the development property of the depmonitor service is set to inherit, the period scan of directories managed by the depmonitor (by default the deploy/ directory) service will be enabled.

WAR archive deployment case (for single or EAR packaged WARs). Each WAR archive is unpacked in the working directory of the JOnAS server in a different folder to avoid file locks. This is especially useful in a Windows environment.

Necessary to enable the onDemand feature of the web service.

Production mode

This mode is recommended in industrial production context.

In case of the development property of the depmonitor service is set to inherit, the period scan of directories managed by the depmonitor (by default the deploy/ directory) service will be disabled.

WAR archive deployment case (for single or EAR packaged WARs). 

Each WAR archive is unpacked in the working directory of the JOnAS server in the same folder.

Force the disabling of the onDemand feature of the web service.