How to handle fault event using Cairngorm?

Question

Hi,
I have started using Cairgorm framework recently. But in this, I'm not able to figure out a place to handle a fault event. Based on some tutorial, here's my Command code:
public class LoginCommand implements ICommand, IResponder{
        public var model:ViewModelLocator = ViewModelLocator.getInstance();
        public function LoginCommand(){
        public function execute(event:CairngormEvent):void{
            var loginEvent:LoginEvent = event as LoginEvent;
            var delegate:LoginDelegate = new LoginDelegate(this);   
            model.userName = loginEvent.loginAttempt.userName;
            model.password = loginEvent.loginAttempt.password;
            delegate.login(loginEvent.loginAttempt);
        public function result(data:Object):void{
            model.applicationState = model.constants.MAIN_SCREEN;
            model.acCarbonFootPrint = data.result.EtCarbonFootPrint;
            model.acVariants = data.result.EtVariant;
            model.acBuildings = data.result.EtBuilding;
            model.cbLabelField = model.constants.FIELD_DESC_NAME;
            CursorManager.removeBusyCursor();
        public function fault(info:Object):void{
            CursorManager.removeBusyCursor();
            var faultEvent:FaultEvent = FaultEvent(info);
            Alert.show("Some fault...");
If the return from the webservice is successful, it get's into result function. But if there is something wrong(like URL is offline), it wont get inside the fault function. Instead I get a runtime error. Here' a screen shot which depicts the dispatch of fault event from WebService.as:
Is there some other place\function where I can catch this fault event?
-Deepak

Answer 1

Usually, if there is a mismatch in data type (input character length exceeds the number that is defined for a field at backend DB table), I get a faultCode:DecodingError
faultString:SOAP Response cannot be decoded. Raw response:
This fault event will be caught in the fault function in the code above.
But it is not catching the faultCode, Server.Error.Request and it's not triggering the fault function.................