OnRails.org

The observer also disapeared, so here i try again with textile… [crossing fingers]

I set up my rails models with validations.

I then call a save! in my service (as this throws an error). This error triggers the Fault method in my cairngorm command:

public function fault(info:Object):void
{
  try{
    var i:FaultEvent = FaultEvent(info);
    PoolManModel.getInstance().serverValidationMessages = ArrayUtil.toArray(i.fault.faultString);
  } catch(error:Error) {
    Alert.show("ouch:" + error.message, "mas problemas");
  }
}

The next part is a remote validator class:

package view
{
    import mx.validators.Validator; 
    import mx.validators.ValidationResult;
    import com.adobe.cairngorm.model.ModelLocator;
    import models.PoolManModel; 
    public class RemoteValidator extends Validator { 

        // Define Array for the return value of doValidation(). 
        private var results:Array; 

        public function RemoteValidator() { 
            // Call base class constructor. 
            super(); 
        } 

        // Define the doValidation() method. 
        override protected function doValidation(value:Object):Array { 
            results = super.doValidation(value);        
            // Return if there are errors. 
            if (results.length > 0) 
                return results; 

            var result:Array = new Array();
            var messages:Array = PoolManModel.getInstance().serverValidationMessages;
            for (var i:int=0; i < messages.length; i++){
                result.push(new ValidationResult(true, null, "NaN", messages.pop())); 
            }
            return result;
        } 
    } 
}

Now, how do we make sure the doValidation is triggered?

I add an observer (thanks Alex Uhlmann) to my view, here you see them side by side:

<view:RemoteValidator id="userNameValidator"  source="{user_name}" property="text" required="true" /> 
<ac:ObserveValue handler="triggerRemoteValidator" source="{model.serverValidationMessages.length}" value="true"/>

What do you think?

Thanks for feedback. I will have to play with that as I was strungling finding how to trigger a Fault and pass information back to the Flex app. So maybe thats the anwser. I will play with it once I am back from the 360Flex conference.

This is a Flex-only solution, however, because the Rails server sends a 200/OK status code even when there is an error. Ideally, the Rails server would send the error messages in XML, as it is doing in this article, but also send an error status code such as 400/Bad-Request.

That way, the Rails server works with non-Flex clients.

Does anyone have a solution for sending non-success (non 2xx) status codes to Flex along with error messages?

Nice work. I don’t seem te be able to find the RailsErrors class though. Is it possible to post it also. Thanks.

Hi Herman,

You can get the RailsErrors class here http://nouvelles-solutions.com/onrails/activeresourceclient/ActiveResourceClient.zip

This zip file contains the following files:

ActiveResourceClient.mxml

FixtureResource.as

RailsErrorBox.mxml

RailsErrors.as

RailsValidationForm.as

Use at your own risk ;-)

The wheelerstreet article link is broken. Any chance of that bieng archived somewhere?

The original article was on http://blog.wheelerstreet.com/?p=123. There is a Flex demo application in the article on which you can do a view source. The source is visible here http://blog.wheelerstreet.com/code/formValidator/srcview/index.html