2.4.3. depmonitor service configuration

The depmonitor service scans periodically some directories in the aim of deploying J2EE applications or OSGi bundles on a JOnAS server. By default, you have to put the application files into the $JONAS_BASE/deploy directory in order to deploy them. It is possible to parse anothers directories by setting the directories property in the service configuration.

The development attribute in the configuration allows to choose if the depmonitor service is in development mode or not :

As the parsed directories may contain files that must not be deployed, a list of file exclusions can be defined.

###################### JOnAS Deployment Monitor
#
# Set the name of the implementation class of the depmonitor service
#
jonas.service.depmonitor.class          org.ow2.jonas.deployablemonitor.DeployableMonitorService

# Set the execution mode (three possible values):
# - inherit: inherit of the value of the "jonas.development" property 
# - true   : development mode
# - false  : production mode
jonas.service.depmonitor.development    inherit                                      1

jonas.service.depmonitor.directories                                                 2 
# List (comma separated) of exclusion patterns (based on names, not directories)          
jonas.service.depmonitor.exclusions     README                                       3

# Monitor interval in milliseconds
jonas.service.depmonitor.monitorInterval    5000                                     4

1

If the property value is true, the directories are parsed periodically to detect file addition, modification or deletion. Else, the directories are parsed only at startup

2

A comma-separated list of directories which contain files to deploy

3

A comma-separated list of file names to exclude

4

Monitor interval in milliseconds between two scans