Comparing current revision with historical revision 4.
From line 21 changed to line 21:
Here is my tutorial to combine Seam and Flex. I will use Seam 2.1, Flex SDK 3.3 and FlamingoDS 1.7. See the [following post=>http://seamframework.org/Community/DirectSeamSupportForFlex] to learn why I'm using FlamingoDS and not GraniteDS or BlazeDS.
From lines 23 to 24 changed to lines 23 to 159:
here is my tutorial to combine Seam and Flex. I will use Seam 2.1, Flex SDK 3.3 and FlamingoDS 1.7. See this post to learn why I'm using FlamingoDS and not GraniteDS or BlazeDS.
=basic Seam 2.\*-project =( e.g. created with seam-gen)
=install Flex SDK 3.3 =set |FLEX_HOME| =configure IDE =configure compilation (e.g.: flexTasks with ant) =(config AS-generation with GraniteDS, if needed)
<b>2) configure FlamingoDS</b>
=[download=>http://www.exadel.com/web/portal/flamingo] =(version 1.7. is used here, version 1.8 is available since 01.06.09)
<b>2.2) Java libraries</b>
=add these libraries into classpath: amf-serializer-1.7.1.jar, flamingo-service-1.7.1.jar
<b>2.3.) Flex libraries</b> To use flamingo seam components, the compiler needs to know the flamingo-flex-1.7.1.swc(/WEB-INF/lib/flex/) library; e.g. via ant:
<b>2.4) configure AMF-Servlet</b> FlamingoDS allows us to acces Seam components as RemoteObjects. For that reason, AMF(Action Message Format)-protocol is used to transform Java objects into AS objects and vice versa. Flamingo provides a Servlet to manage the communication between frontend and backend. It's registered in the web.xml:
The name in "destination" equals the name of the Seam component.
<b>3.3) Access from MXML</b> The SeamRemoteObject is one of the client-components Flamingo provides to control conversations. Simply assign the Seam component as remote object and it is available within Flex mxml source-file. There is no need for further initializations: