Posts Tagged fix
Mac Flash Builder Plugin Install Error 6 + FIX
Posted by brianr in eclipse, flash builder, mac on October 8th, 2010
I just received my new 17in MBP so I pulled down a new version of Eclipse’s J2EE IDE and installed Flash Builder Plugin.
NOTE: You need to use the Eclipse Galileo Packages and the Carbon Install in order for this to work since FB is not compatible with the latets Eclipse build called Helio — here’s a link to the exact version of Eclipse that I used.
After a seemingly successful installation I received the following error code when starting up Eclipse: Error 6. I googled around a bit and found this link with this important tid-bit that fixed my issue:
- Reboot your Mac
- Navigate to your installation folder under /Adobe Flash Builder 4 Plug-in/install.support/AdobeFlashBuilderPluginSTIWrapperMac/
- Run Install.app from that location, to make sure all the required runtimes are installed successfully.
The restart seemed to do nothing, but running the installer did the trick. Good luck!
Workaround to Flex SDK 3.4 Bug 22333 :: HTTPService Responders Are Called Twice…Here’s a Fix!
Posted by brianr in actionscript, flex on September 29th, 2009
This one kicked my team’s ass for a couple of hours so I’m hoping it’ll help somone else…so we updated our Flex SDKs to 3.4 and all of a sudden all of our Delegates’ result handlers were getting called twice. We thought it was due to our service orchestration object (we have a base object that allows us to make sequential Cairngorm service calls) and somehow we were calling the services 2x, but nope…wasn’t it. Seemed our AbstractDelegate that sets up the responders for all of our service calls like so had the issue:
public function executeHTTPService(requestDTO:AbstractRequestDTO=null):void
{
logger.debug("executeHTTPService");
var token:AsyncToken;
var responder:mx.rpc.Responder;
// create a responder for the service
responder = new mx.rpc.Responder(result, fault); // WTF mate?
// execute the service
token = this.service.send(requestDTO);
token.addResponder(responder); // why yall busted up now???
}
Apparently, SDK 3.4 reintroduces an old defect that causes this implementation of setting up the responder with the async token to call the result handler twice…bummer, eh? So what to do…well, a simple workaround until they fix this is to do the following:
this.service.addEventListener(ResultEvent.RESULT, result); this.service.addEventListener(FaultEvent.FAULT, fault);
Just create your handlers with good-ole fashioned event handlers…DONE.
Get more info on the defect here.