Running a Jade Client Application using jade.exe

You can run any application type run from the client, including a standard (fat) client, a thin (presentation) client, non‑GUI applications, and so on, using the jade.exe executable.

When initiating a Jade client application using the Jade executable (jade.exe), you can collect strings (arguments) from the command line and pass them to the initialization method of the application. Only the application initiated using the command line arguments uses these command line arguments.

To run a Jade client application using the jade.exe

• The arguments recognized in the command lines are startAppParameters and endAppParameters.

• The elements between the startAppParameters and endAppParameters arguments are added to a transient HugeStringArray object that is created.

  The added elements are a unary string (for example, DailyTests) or a coupled pair separated by a = character (for example, codeCoverage=true). For example, startAppParameters c:\jade\unittest.xml DailyTests codeCoverage=true profile=true c:\jade\logs\unittest.log endAppParameters results in a HugeStringArray of:

  1. c:\jade\unittest.xml

  2. The test name (that is, DailyTests)

  3. codeCoverage=true

  4. profile=true

  5. c:\jade\logs\unittest.log

• The built HugeStringArray object is passed to the defined initialize method for the invoked application. That method must therefore expect a parameter of a HugeStringArray type. If not, exception 4027 (Method called with incorrect number of parameters) is generated for the parameter mismatch.

When processing the elements after the startAppParameters argument:

• The elements are separated by spaces.

• Leading and trailing spaces in each string element are removed.

• All subsequent arguments up to the endAppParameters argument or the end of the command line are collected into a HugeStringArray and passed to the initialize method.

• Any double or single quotes around elements are dropped.

• Any spaces just before and directly after the = sign are dropped.

Note also:

• If no such command line arguments are specified, the initialize method is passed a null value if it requires a parameter.

• Any spaces just before and directly after the = sign are dropped. The = sign and the value are passed through as a single string in the HugeStringArray.

• The created transient object is deleted when the initialize method call completes.

• This feature applies only to the application being initiated from the command line of jade.exe.

The following example specifies the Jade executable (jade.exe) command line for the non‑GUI JadeUnitTestBatch application.

jade path=c:\jade\system schema=TestUnitTestSchema ini=c:\jade\system\jade.ini app=JadeUnitTestBatch appServer=MyAppServer appServerPort=1234 startAppParameters c:\jade\unittest.xml DailyTests codecoverage=true profile=true c:\jade\logs\unittest.log endAppParameters

The following example specifies the Jade executable (jade.exe) command line for the GUI No Forms JadeUnitTestGuiNoForms application.

jade path=c:\jade\system schema=TestUnitTestSchema ini=c:\jade\system\jade.ini app=JadeUnitTestBatchGuiNoForms appServer=MyAppServer appServerPort=1234 startAppParameters c:\jade\unittest.xml DailyTests codecoverage=true output=true c:\jade\logs\unittest.log endAppParameters

The JadeSchemaLoader application enables you to deploy schema changes directly, without having to stop any applications that are running. For details and an example, see "JadeSchemaLoader Application", in the Schema Load User's Guide.

For details about loading exported user preferences from the jade (or jadclient) executable command line, see "Loading User Preferences from the Command Line", elsewhere in this chapter.