Here the properties and methods used by EntityValidator are described.

Seam or Spring component named com.exadel.flamingo.service.validator.entityValidator is used on the server side to manage validation processing. See Java documentation for class com.exadel.flamingo.service.validator.EntityValidatorImpl for more information.

<context:component-scan base-package="com.exadel.flamingo.service"/>

See a sample below:

package com.mycompany.myproject;
import org.hibernate.validator.Length;
import org.jboss.seam.annotations.Name;
import javax.persistence.Entity;

@Name("person")
@Entity(name="Person")
public class PersonBean {

    private String lastName; 

    @Length(min=3, max=40)
    public String getLastName() {
        return lastName;
    }

}

<flamingo:EntityValidator id="validator"
  destination="person"
  source="{valueId}"
  validationTarget="lastName"
  property="text" />

<mx:Form>
    <mx:TextInput id="valueId" />
    <mx:Button label="Validate" click="validator.validate()" />
</mx:Form>

In this example when the "Validate" button is clicked, the validation request is sent to the server where text entered into the valueId field will be validated for the Hibenate Validator @Length annotation correspondence (and any other Validator annotation presented at lastName).

An example of validation using the HessianEntityValidator component can be performed the same way as with the help of EntityValidator. Just use this code sample for your .mxml file:

<flamingo:HessianEntityValidator id="validator" 
  destination="seam/resource/hessian/person" 
  validationTarget="lastName" 
  source="{test}" 
  property="text" />

<mx:Form>
    <mx:TextInput id="test" />
    <mx:Button label="Validate" click="validator.validate()" />
</mx:Form>

See a real example how to use the Validator component in the "validation" sample project in Flamingo bundle.

Here the properties, events and methods used by CallSet are described.

Seam or Spring component named com.exadel.flamingo.service.callset.callSetManager is used on the server side to manage CallSet processing. See Java documentation for this class for more information.

<context:component-scan base-package="com.exadel.flamingo.service"/>

<mx:Script>
    <![CDATA[
        private function loginResultHandler(event:ResultEvent):void
        {
            var results:Array = event.result as Array;
            if (results[3])
            {
                Alert.show('Successfully logged in');
            } else {
                Alert.show('Login failure');
            }
        }
    ]]>
</mx:Script>
        
<flamingo:CallSet id="loginCallSet" 
  result="loginTestResultHandler(event)"
  destination="callSet">
    <flamingo:Call component="identity" method="setUsername"/>
    <flamingo:Call component="identity" method="setPassword"/>
    <flamingo:Call component="identity" method="login"/>
    <flamingo:Call component="identity" method="isLoggedIn"/>
</flamingo:CallSet>
        
<mx:Button id="loginBtn" label="Login" click="loginCallSet.send(["flamingo"],["secret"],[],[])"/>

This sample shows the way the CallSet component is used to bundle 4 server method calls in one server request to authenticate a user via the identity Seam component.

<services-config>
    <services>
        <service
            id="binding-service"
            class="flex.messaging.services.RemotingService"
            messageTypes="flex.messaging.messages.RemotingMessage">
            <destination id="callSet"/>
            <default-channels>
                <channel ref="seam-amf"/>
            </default-channels>
        </service>
    </services>

    <channels>
        <channel-definition id="seam-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint
                uri="http://{server.name}:{server.port}/myapp/seam/resource/amf/"
                class="flex.messaging.endpoints.AMFEndpoint"/>
        </channel-definition>
    </channels>
</services-config>

Flamingo supports execution of the whole CallSet inside of one transaction for a project with EJB support. In order to do that, add the following string into the “components.xml” file:

<component name="com.exadel.flamingo.service.callset.callSetManager" class="com.exadel.flamingo.flex.callset.EJBCallSetManager"/>

See a real example how to use the CallSet component in the "callSet" sample project in Flamingo bundle.

<flamingo:HessianCallSet id="loginCallSet" 
  destination="seam/resource/hessian/"
  result="loginTestResultHandler(event)">
    <flamingo:SeamHessianCall component="identity" method="setUsername"/>
    <flamingo:SeamHessianCall component="identity" method="setPassword"/>
    <flamingo:SeamHessianCall component="identity" method="login"/>
    <flamingo:SeamHessianCall component="identity" method="isLoggedIn"/>
</flamingo:HessianCallSet>

Here the properties, events and methods used by BindingService are described.

Seam or Spring component named com.exadel.flamingo.flex.binding.bindingManager is used on the server side to manage binding processing. See Java documentation for this class for more information.

<context:component-scan base-package="com.exadel.flamingo.service"/>

package com.mycompany.myproject.seam;

import org.jboss.seam.ScopeType;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.annotations.Scope;

@Name("personBean")
@Scope(ScopeType.SESSION)
public PersonBean{

    private String firstName;
    private String lastName;

    public String getFirstName() {
        return firstName;
    }

    public void setFirstName(String firstName) {
        this.firstName = firstName;
    }

    public String getLastName() {
        return lastName;
    }

    public void setLastName(String lastName) {
        this.lastName = lastName;
    }
}

package com.mycompany.myproject.flex.vo
{
	[RemoteClass(alias="com.mycompany.myproject.seam.PersonBean")] 
	[Bindable]
	public class PersonVO
	{
		private var _firstName:String;
		private var _lastName:String;
		
		public function get firstName():String
		{
			return _firstName;
		}
		
		public function set firstName(value:String):void
		{
			_firstName = value;
		}
		
		public function get lastName():String
		{
			return _lastName;
		}
		
		public function set lastName(value:String):void
		{
			_lastName = value;
		}
	}
}

<mx:Application creationComplete="init()">

	<mx:Script>
		<![CDATA[
			import com.mycompany.myproject.flex.vo.PersonVO;
			import mx.controls.TextInput;

			[Bindable]
			private var user:PersonVO;
			
			private function init():void 
			{
				user = new PersonVO();
				user.firstName = "John";
				user.lastName = "Smith";
			}
		]]>
	</mx:Script>
       
<flamingo:BindingService id="personBinding" 
    destination="personBean" 
    source="{user}" />
       
<mx:TextInput text="{user.firstName}"/>
<mx:TextInput text="{user.lastName}"/>
<mx:Button label="Send data to server" click="personBinding.commit()"/>
<mx:Button label="Get data from server" click="personBinding.update()"/>
</mx:Application/>

Binding synchronizes object with any level of hierarchy of nested objects/collections. In case if collection is sent from the server to the client using Hessian, the content of this collection will be deserialized into objects of the Object class, i.e. the original object class will not be restored (see Known Issues in the Supported Protocols section related to binding: "mx.collections.ArrayCollection", "Deserialization to ActionScript Classes").

Object structure on client side defines a level of hierarchy binding will be performed with.

In order to take the most advantage from binding, use [RemoteClass] metadata for AMF and hessianTypeName class variable for Hessian (see an example below). Otherwise objects coming from the client side to the server will be deserialized into HashMap and collections will be filled with HashMap objects if generics for collections are not used on the server.

Currently no "stale data" events are generated during the commit/update operations; objects are not merged but completely overwritten.

Flamingo supports binding inside of one transaction for a project with EJB support. In order to do that, add the following string into the "components.xml" file:

<component name="com.exadel.flamingo.flex.binding.bindingManager"  class="com.exadel.flamingo.flex.binding.EJBBindingManager"/>

See a real example how to use the Binding component in the "binding" sample project in Flamingo bundle.

The code sample for HessianBindingService is almost identical to the sample provided for BindingService component, see below:

<flamingo:HessianBindingService id="personBinding" 
	destination="seam/resource/hessian/personBean" 
	source="{user}" />

Here the properties and methods used by HessianEntityValidator are described.

Seam or Spring component named com.exadel.flamingo.service.validator.entityValidator is used on the server side to manage validation processing. See Java documentation for class com.exadel.flamingo.service.validator.EntityValidatorImpl for more information.

<context:component-scan base-package="com.exadel.flamingo.service"/>

See a sample below:

package com.exadel.flamingo.javafx;

import javafx.stage.Stage;

import javafx.scene.Scene;

import javafx.scene.text.Text;

import javafx.scene.text.Font;

import javafx.scene.layout.HBox;

import javafx.scene.paint.Color;

import javafx.scene.text.TextOrigin;

import javafx.ext.swing.SwingButton;

import javafx.scene.layout.VBox;

import javafx.scene.control.TextBox;

            

import com.exadel.flamingo.javafx.components;

            

var validator = HessianEntityValidator {

          destination: "person" 

          property: "lastName"

}

            

var textField: TextBox = TextBox {

      text: "test"

      columns: 7

      selectOnFocus:true

}

            

var sampleLabel = Text{

      y: 8

      font: Font { name:"sansserif", size: 12 }

      fill: Color.BLACK

      content: bind validator.returnedMessage

      textOrigin: TextOrigin.TOP

}

            

var validateButton = SwingButton  {

       text: "Validate"

       action: function(){

              validator.validate();

        }

}

            

Stage {

            width: 300

            height: 200

            title: "Validation Sample"

            scene: Scene {

                content: VBox {

                        translateX: 5

                        translateY: 5

                        spacing: 10

                        content: [                

                                HBox {

                                          content: sampleLabel

                                          spacing: 10

                                 },

                                 HBox {

                                                           content: textField

                                            spacing: 10

                                 },

                                 HBox {

                                                           content: validateButton

                                             spacing: 10

                                 }]

                        }

            }

}

            

          

In this example when the "Validate" button is clicked, the validation request is sent to the server where text entered into the textField field will be validated for the Hibenate Validator @Length annotation correspondence (and any other Validator annotation presented at lastName).

If there is any validation error message it will be displayed in the SimpleLabel.

See the server code sample in 5.1.1.1.3: Code Sample