11
Mar
2009
AMFPHP + Flex 3 = Error [unable to open 'services-config.xml']
While trying to configure the AMFPHP set up with the Flex 3 framework I ran in to a problem while setting up the services-config.xml.
I’ve created the file in the root directory and specified in the Flex Compiler [Additional compiler arguments] the following string -locale en_US -services “services-config.xml”.
As soon as I clicked OK an error popped up with a message unable to open ’services-config.xml’. After trying varying things I was able to figure out that the problem was with the location of the file. Simply placing the file at the root of the directory wasn’t the right location. I needed to put the file in the same directory as the main MXML executable – after that the program worked as expected.
5
Mar
2009
Cooking with Stacy and Max
After a successfull attempt to prepare a Cod, Potatoe & Leak soup along with a side serving of Russian home cooked crapes I’ve decided to start a new website that documents our adventures.
Cooking with Stacy and Max can be foudn here.
2
Mar
2009
Adobe Flex online tutorials
A great collection of tutorials for anyone who is interested in learning how to work with Adobe Flex. The lessons cover everything from the basics of Flex Builder to more complicated topics like building run time shared libraries. Have a look and learn something new.
23
Jun
2008
Adobe Flex Builder 3 short dump [JVM terminated. Exit code=1...]
|
I was using Adobe Flex Builder 3 [AF3] for a few weeks now. I like what has been done with the application, the new functionality is very useful and there is a ton of new options that can be configured while designing your applications. Unforchunately similarly to it’s predecessor there are major bugs in AF3. A week ago for no apparent reason the application stopped working. Every time ran the application it threw a short dump before initializing the EDI. |
 |
I’ve tried reinstalling the application and even removed the old versions of JRE references. Nothing helped and just as before I had to rely to googling and looking at configuration files.
The problem lied in the small FlexBuilder.ini file located in the root installation directory. The contents of the file included the following settings:
-vmargs -Xms128m -Xmx512m -XX:MaxPermSize=256m -XX:PermSize=64m -Djava.net.preferIPv4Stack=true
I’ve modified the contents to exclude the last lines and vuala, the application went back to it’s usual state [sure I lost all my projects but its nice to have a working EDI once again].
