I updated my “Tomcat Launcher” sample application for AIR 2.0 GA.
“Tomcat Launcher” allows you to start / stop Tomcat and view the standard output log without opening a DOS box or Terminal window. It also allows you to open that log in your default Text Editor which is another new feature of AIR 2.0 that I covered in the “AIR2Excel” sample application. Tomcat Launcher also provides a generic example showing how to use the AIR 2.0 native process API to execute Java code.
Installation Instructions
- Make sure you have the AIR 2 runtime installed (you can download it here).
- Because Tomcat Launcher uses the Native Process API, you have to use a native installer:
- To install the application on Windows, download and run TomcatLauncher.exe.
- To install the application on a Mac, download and run TomcatLauncher.dmg.
After starting the application, enter the paths to your Java home folder and to the Tomcat installation you want to start, then click the Start button. The application will remember the folders you entered the next time you use the application. If you get a BindingException, make sure Tomcat isn’t already started. You can also click the Stop button to stop a running instance.
You can download the project here: TomcatLauncher.fxp.zip.
NOTE: If you want to compile the project, make sure you use the AIR 2 SDK available here.

hello My name is Larry Eliemenye
i would like to get your assistance on something i’m working on….
I am creating an AIR app that receives input from a game controller through a Java console application which i bundled into an exe file. The Files needed for the java Console Application to work well are the main Class file, and a plugin called JInput which takes care of talking to the controller hardware.
this application works normally when run outside AIR as standalone… but using AIR’s native process API, it doesn’t seem to return anything from the output/Error Stream!
my nativeprocessStartupinfo.executable property points to the .exe file and i’m not passing any arguments to the application
Any form of help will be appreciated
thanks
Of course, entire thing fails miserably if you have a space ” ” in any of your NativeProcessStartupInfo.arguments. So much work building this API goes to nothing for a single act of sloppiness.