
I'm working more with FDT nowadays in addition to Flash and Flex. FDT is a cool product and certainly brings some nice features to the table.
I did, however, have a little problem when I first installed the FDT Enterprise Standalone on my Windows XP machine - where Flex Builder 3 was already installed and running nicely.
After installing FDT Enterprise and quickly putting together a little test package and script I hit the "Run" button. The result was an error message I hadn't expected:
Error: could not find a JVM.
Interesting, when you consider that FDT, like Flex, is based on Eclipse and therefore needs a JVM to even run!
So, it was time to surf around and try to work through the potential issues with my friends at Powerflasher ![]()
We spent an hour going through various settings and ideas. Finally a small difference the Windows JAVA_HOME setting mentioned by Maxim from Powerflasher got me curious.
Flexbuilder 3 had set this environment variable to "C:\Program Files\Adobe\Flex Builder 3\jre\bin" whereas Maxim's Windows JAVA_HOME was set to "C:\Program Files\Adobe\Flex Builder 3\jre"
I deleted the "\bin" to point the variable at the root level of the JRE install, restarted FDT, hit "Run" and hey presto - it ran!
So, if you get this issue, check your JAVA_HOME environment variable and drop the "\bin".
Flexbuilder 3 still runs perfectly too.
Thanks to Tilman, Maxim and Steffi from Powerflasher for their help!











Recent comments