Välkommen till Callista Enterprise blogg - här finns tekniska artiklar, presentationer och nyheter om arkitektur och systemutveckling. Håll dig uppdaterad genom att följa oss på Twitter.
Callista Enterprise medarbetare Jan Västernäs

Integrating Flex, BlazeDS and Spring

// Jan Västernäs

Suppose you have an web application with a service layer implemented by spring beans and want to get a richer user interface ? One way to do it to use Flex.

Parts of the Flex development platform has become Open Source. What you absolutely need is addition to that is the Flex Builder. It enables debugging of the Flex application and without that you are completely lost. The license is 150 Euro so it is no big deal.

So the User Interface is produced using Flex and to take care of the remoting we can use BlazeDS which is Open Source from Adobe. BlazeDS is deployed as an web appication.

My Helloworld sample version 1 uses a simple java class on the server side. Version 2 will use spring.

The class has a method

public List<Topic> getAllTopics()

Topic contains two attributes speaker and name.

In Flex I define a RemoteObject to describe the communication with the server

<mx:RemoteObject id="server" destination="cadec-service">
  <mx:method name="getAllTopics" result="getAllTopicsResult(event)" />

The method tag tells Flex that whenever the getAllTopics Method is called the return value will be handled by the getAllTopicsResult method which is defined like this

private function getAllTopicsResult(event:ResultEvent):void	{
    topics = event.result as ArrayCollection;

It simply saves the result to a variable topics. Finally a DataGrid is defined to display the result

<mx:DataGrid dataProvider="(topics)">
    <mx:DataGridColumn dataField="speaker" width="150"/>
    <mx:DataGridColumn dataField="name" width="350"/>

When the page is loaded a call to getAllTopics is made

<mx:Application . . . creationComplete="server.getAllTopics()">

and when the reply arrives the grid is populated and looks like this

Bild saknas

BlazeDS need to know what the destination=”cadec-server” means. The information is supplied in file named remoting-config.xml

<destination id="cadec-service">

This will create an instance of the CadecService (each time). The classes are put in WEB-INF classes.

HelloWorld sample version 2 uses spring on the server side.

To enable that I followed the instructions outlined by http://coenraets.org/flex-spring/

2 classes SpringFactory.class and SpringFactory$SpringFactoryInstance.class needs to be present att WEB-INF/classes.

To enable the spring integration these classes needs to be configured in the services-config file

  <factory id="spring" class="flex.samples.factories.SpringFactory"/>

Now the remoting-config.xml destination can be changed to use the SpringFactory to get the bean from spring instead of initializing it. Obviously this means that the CadedService class will only be instatiated once.

<destination id="cadec-service">

Now everything works again.

If this wasn’t simple enough we just have to wait for the new spring/flex integration project to deliver


Tack för att du läser Callista Enterprise blogg.
Hjälp oss att nå ut med information genom att dela nyheter och artiklar i ditt nätverk.