This package allows to trigger en action when a json file describing is writte in the ${jeebop.home}${/}triggers directory.
The action implementation class must implement the jeebop.trigger.ActionTrigger interface.
An example of a json trigger, for the jeebop.trigger.PackageInfo action trigger, is :

{
	"actionClass" : "jeebop.trigger.PackageInfo",
	"parameter" : [
		"name=jeebop.biomed.result.trend",
		"output=-",
		"debug=true",
		"printVersionComment=false"
	]
}

The action can be executed in a dedicated thread, if the getter getUseThread() returns true.
The action object is instantiated through the default constructor. The method setParameter(String name, String value) will be called for each parameter entry of the json file, which will be split arround the = sign.
Once the instance is initialized, 2 methods are called prepareAction() and triggerAction() to prepare and process the action.
There are some dynamic config properties which control the trigger watcher execution :

trigger.watch.period which specifies, in seconds, the polling timeout of the watcher. The default value is 5s,
trigger.watch.debug which, if true , will print debugging traces in jeebop.out
trigger.watch.fire-delay.implementation_class_name which specifies, in seconds, a minimum period between 2 execution of the same action trigger. The default value is 1s. If an execution is triggered during this period, it is skipped and the trigger file is deleted.
trigger.file.time2live which specifies, in milliseconds, the time to live of an incomplete or faulty json trigger.

The trigger system is started as an external system with the implementation class jeebop.trigger.Watcher and needs it's dedicated thread.
The jeebop.trigger package contains two trigger action implementations :

jeebop.trigger.PackageInfo which allows to print informations on the classes of a package from the Jeebop class loader. See the aforementioned json example.
An example snippet of the output generated by this implementation is :

{
  "name" : "jeebop.biomed.result.trend",
  "classInfo" : [ {
    "lastVersion" : 1,
    "lastVersionDate" : "17/06/2019",
    "name" : "jeebop.biomed.result.trend.TrendDataIterator",
    "url" : "file:/home/jdev/0470/classes/jeebop/biomed/result/trend/TrendDataIterator.class"
   }, {
    "lastVersion" : 3,
    "lastVersionDate" : "24/02/2023",
    "name" : "jeebop.biomed.result.trend.ConstantChartGenerator",
    "url" : "file:/home/jdev/0470/classes/jeebop/biomed/result/trend/ConstantChartGenerator.class"
    }, {
...
    }
  ]
}

jeebop.trigger.CpuInfo which triggers the dump of the Jeebop CPU Monitor to ${jeebop.base}${/}logs${/}monitor-dump.log file. In order to work, the JeebopMonitor external system must be active.

The jeebop.trigger.Tools class allows to generate and print a json configuration scheleton for an action trigger class, to be passed as the main argument. In order to print the parameters values, the class must have getters and setters for each parameter.
The class also allows to generate and print the external config element to be integrated to the server.xml configuration, in order to start the triggers monitor.

The trigger json file, or any other file, can be sent to the server with the jeebop.tools.DeployTool class, using the deploy utility as for exemple :
deploy.sh -u admin -p admin -t FILE -o put -n triggers/cpath.json -f cpath.json
and a result file, or any other file, can be retrieved from the server, using the deploy utility as well, as :
deploy.sh -u admin -p admin -t FILE -o get -n repository/logs/monitor-dump.log -f mdump.log