Using executors

Executor is the part of Pax Runner that is responsible with starting up the target platform.
You can think of executors as "what will happen when pax runner has finished its bootstrapping+provisioning job?"

To use a different executor then the default one you can use the --executor option:

pax-run --executor=<name>

Here is a list of currently supported executors:

Default Executor

Pax Runner will

• create the target platform inside a workingFolder (default: ./runner).
• construct a java vm commandline
• execute it in a new system process immediately

pax-run

Do Nothing Executor

All like Default Executor but will not launch the new process.
Pax Runner will just exit.
Useful when you want to provision a workingFolder now but run the process later.

pax-run --executor=noop

In Process Executor

All like Default Executor but will launch the target platform in-place in the same vm as pax runner.
Note: this heavily limits paxrunner's capabilities to non-javaVM settings.

pax-run --executor=inProcess

Script Executor

All like "noop" but will preserve the constructed java commandline in shell scripts. (both .sh and .bat.
Scripts will be created in current folder.

pax-run --executor=script

Script & Zip Executor

All like "script" but will zip up workingFolder and script in a zipfile.
With this you can ship fully set up application produced by paxrunner to another machine, extract there and launch (generated) launch script.

pax-run --executor=zip

Init.d Script Executor

All like "script" but will preserve the constructed java commandline in script along with Unix init.d start/stop/restart semantics.
Script will be created in workingFolder.

pax-run --executor=init.d,MyApp