Today I added a new feature to Transmission which allows for debugging the java side of your application. The step-by-step details for making it work are as follows (I will be using the TransmissionDemo project in the repo to illustrate this).
1. An optional parameter has been added to the init method of the Flex side of Transmission which by default sets remote debugging to true. Make sure that in production this parameter is set to false.
![]()
2. Open up Flash Builder, and import the TransmissionDemo and Transmission projects. Then run the TransmissionDemo project. Now it’s time to set up the Eclipse debugging environment. Minimize the AIR application for now…
3. Open up Eclipse and import the TransmissionDemo and Transmission projects.
4. Now we will setup the remote configuration in Eclipse by going to the Debug Configurations screen. Right click on the TransmissionDemo project -> Debug As -> Debug Configurations
5. Now let’s set up the connection. First right click on Remote Java Application and choose New. Next make sure the TransmissionDemo project is chosen. Finally choose Standard (Socket attach), host: localhost, and port: 8000 and then click the Debug button.
5. Set a breakpoint on the first line of the DemoMessageHandler.java file in the TransmissionDemo project within Eclipse.
6. Return to the TransmissionDemo AIR window and click on the “Send Transmission Message” button.
7. You should hit your breakpoint.




Good tutorial.
can transmission as3 used in air application from flash professional or is it just for flex?
Thanks…
I actually haven’t tried Transmission with Flash Professional. It should work fine, but let me know if you run into any problems.
I’m getting “Failed to connect to remote VM. Connection refused.” on OSX. No firewall or anything. What could be causing that?
Make sure you start up your AIR app and that Transmission is started up and running before you try to connect with the remote debugger.
Thanks. Worked. I realize that may be a Noob mistake, however I think it still warrants mention as a “step” above.
Glad it worked! I’ll update the post to be more clear about that.
Wouldn’t it be better if debug info went to both the console and a log (rather than just a log?)