Hi Nico,
I found a document describing how to add extra jars to the process designer.
Overview
In order to obtain full use of the design time features of a QPAC, it is often necessary to add extra jar files to the classpath of the Workflow Designer.
For example:
The SQL Plus QPACs connect directly to the target database in order to populate the databases meta-data.
The Email Receiver QPAC needs to connect via JavaMail so that it can display the contents of any emails if finds on the Test tab.
Unfortunately, the standard Workflow Designer executable does not provide any way to add jar files to the classpath.
This document describes one technique for adding additional jar files to the Workflow Designers classpath.
Note: At runtime, the additional jar files are generally made available by:
Having them in the lib directory of the QPACs jar file
Explicitly adding them to the lib directory of the application server.
Instructions
Obtain a copy of Janel (the Java Native Executable). You can download Janel from
http://sourceforge.net/projects/janel.
There are two Janel executables: Rename JanelWindows.exe to Designer.exe and rename JanelConsole.exe to DesignerC.exe. Please both these files in the Workflow 7.0 Designer directory.
Create two text files named Designer.lap and DesignerC.lap. Both these files should contain the following:
janel.main.class=com.adobe.workflow.tools.processdesigner.PAD
-Djava.class.path=.\qlc\
janel.classpath.jars.dir=.\lib
janel.classpath.jars.dir=.\JBoss-lib
janel.classpath.jars.dir=.\extras
janel.jvm.path=..\_jvm\bin\client\jvm.dll
Create a directory called extras in the Workflow Designer directory. Place any additional jar files that are required into this directory. (There is no need to directly specify the names of the jar files any jar files found in the extras directory will automatically be added to the classpath.)
In order to launch the designer, simply double-click on Designer.exe.
DesignerC.exe is identical to Designer.exe, except it also opens a console window. The console window is often useful when debugging QPAC problems, because it gives the entire stack track of any exceptions that occur, rather than just the name of the exception.
Regards,
Yuri
