How To Crash Eclipse...
February 28 2008 by 
Andrew Powell
I was recently (as in two days ago) working on a project that I was trying to debug on both the server-side and the client (flex) side. I had turned on eclipse debugging for my application server (JBoss 4.0.5GA) and everything was going well. I then tried to debug my Flex app to see if the data going into the server was being put together right and causing the failure server-side. I know Service Capture will show me what's going across the wire, but I wanted to see, for sure that things were being built right in Flex.
Something unexpected (at the time), but not unreasonable happened when I tried to concurrently start Flex Debugging in Ecilpse: Flex Builder bombed out, big time. No errors, no warning, just gone.
The lesson: Debug only one layer at a time and not the whole app front to back.
Posted in Java | Flex | General | Hibernate | Air | 
0 comments