jTask - Tips and Tricks

CLASSPATH issues

jTask and the Java CLASSPATH

There are three places jTask can find classes:

System CLASSPATH
Special "drop folder" (eg, C:\Program Files\jTask\classes)
LAX (LaunchAnywhere Executable) CLASSPATH environment variable.

(if you are not running it as an NT Service, then System CLASSPATH will actually be User CLASSPATH)

System CLASSPATH

There are two caveats here. Since it is the System CLASSPATH, updating the CLASSPATH environment variable under a user account will have no effect, and the directory or jar will not be visible to jTask. The second thing to remember is that you must restart the jTask Service in order for the changes to the System Classpath to be recognized.

Drop Folder

The Drop folder is where you can put classes that you are developing, so that you will not have to restart the jTask service after you re-compile. One caveat hare is that it does not support JAR files.

LAX CLASSPATH

If you want to avoid using a global CLASSPATH such as the System CLASSPATH, you can alternatively put directories or JAR's in the LAX CLASSPATH. In order to do this, simply add the directory or JAR to the jTaskService.lax file (at the root of the directory jTask is installed), to the lax.class.path environment variable. Both /'s or \'s should work as seperators, and there is no need to quote directories containing spaces. After modifying this file, you will need to re-start the service to recognize the changes.

Example:


#   LAX.CLASS.PATH
#   --------------
#   the Java classpath necessary to run this application
#   Can be separated by colons or semicolons

lax.class.path=lib/hsql.jar;lib/Jtask.jar;lib/instantDB.jar;lib/swingall.jar;lax.jar;lib/yourjar.jar;C:\Some path\some directory;