Globally for all events: wrapper.event.default.command.argv.<n> property, or
For a specific event: wrapper.event.<event_name>.command.argv.<n> property.
The "<event_name>" component of the property name can be
either the keyword "default",
or one of the Event Types.
The "<n>" component of the property name is an integer number counting up from "1".
property can optionally be set to allow gaps in the sequence.
It is not possible specify default values for individual elements of a command.
The Wrapper will first look for a wrapper.event.<event_name>.command.argv.1.
If found, it will then only look for the command elements containing the <event_name>.
If it was not found, then Wrapper will look for the wrapper.event.default.command.argv.1 property.
Finding that, it will then look for the remainder of the command using the default event properties.
Note that defining a "default event command" will cause the command to be executed for
every single Wrapper event, including user defined events.
For each entry, you can also have a corresponding strip quotes flag
(stripquotes property = TRUE)
which will remove unescaped quotes from the element when run on Linux/UNIX machines.
This is necessary to allow for file references which contain spaces.
For parameters like the one below, it would not otherwise be possible to decide
when to remove quotes and when to leave them alone.
All other characters except for the followings will remain unchanged.
'\\' will become '\',
'\"' will become '"'
'"' will become ''
wrapper.event.jvm_prelaunch.command.argv.2="Argument with spaces."
Whenever any problems are found while trying to configure an event command,
it can be very useful to enable debugging to help figure out exactly what is happening.
The Java Service Wrapper provides a full set of configuration properties that allows you to make the Wrapper meet your exact needs.
Please take a look at the documentation for the individual properties to see all of the possibilities beyond the examples shown above.