Hint: Start a Java Console Window to diagnose problems in Workflow Designer

Question

Hello -
A trick you can use to try and identify problem you are having using the Workflow deisgner is to turn on the JavaConsole for the designer session. On windows you can do this by modifying the shortcut to start designer. Add the following parameter to the end of the path:
"c:\wf\adobe_livecycle_workflow_7_0_designer.exe" -is:javaconsole
Note the Quotes around the path, and the parameter after the quotes.
This will open a console window along with workflow designer - any exceptions thrown will print a stack trace here (as well as any System.out lines you use in a QPac Dialog etc.) I would recommend using this option all the time as it may help diagnose issues.
In the case if mis-matched versions on the server and client you can expecct errors like "InAuthenticPrincipalException", "InvalidClassException" or SerialVersionUID mis-match.
Hope this helps,
Will

Answer 1

I have created two projects, one by Java and the
other one by VC++. Now I want to start the VC++ app,
which is a console app, in the Java program. I tried
using "Runtime.getRuntime().exec(path of VC app)",
but it doesn't work. Even I found with this way, the
Window cmd line cannot be started either. Coz this VC
app is console based, I suspect if there are some
restrictions on the Window Console App to be called
by this Runtime class. Could anybody here help me
with that? Thanks a lot!No. There often seems to be some confusion about how the exec methods work and the restrictions since it is coming from Java.
Let me clear that up.
That is 100% rubbish.
When runtime exec "doesn't work" it means that you have not used it correctly or understand the environment in which it is running or a a myriad of other confusions. But this question gets asked alot and about one point I cannot be more clear. There is NOTHING special happening because it is Java. Windows or Linux or whatever you are running is NOT saying "Well I won't run that program run because it is Java and I hate it. Ha ha!"
No. What it means when it "doesn't work" is that either the OS is saying "what they hell did you just say?" or because the OS says "okay" and does something that you didn't expect.
At any rate please read the following article that has helped many before you http://www.javaworld.com/javaworld/jw-12-2000/jw-1229-traps.html