Hi Jerry,
 
I am doin some R&D on flex intergration with J2EE. I ve some doubts.  
 
 * How do I navigate from one mxml page to another.. feature similar to that of RequestDispatcher or do you any alternate approach. 
 
Remember that the RequestDispatcher in the Servlet API is tied to the request/response paradigm enforced on us by HTTP and the page-request model of a website.
 
With RIA development, we can break free of the shackles of request/response, to a pseudo-thick-client model.  Instead of thinking in pages, we think in terms of an application where our only server round-trip is for RPC method invocation and the exchange of data.
 
So ... rather than dispatch the request forward to view another JSP, it's MUCH easier to simply have your RIA client "render" another view state that already exists on the client.
 
It's a bit of a head-warp, but once you get your head around it, it's liberating, I assure you...
 
* Is there any framework kindoff for intergrating Flex with J2EE application. 
 
Funny you should say that ... check out:
 
http://www.iterationtwo.com/open_source_cairngorm.html
 
With Cairngorm, we took what we consider to be the appropriate patterns from the Core J2EE Pattern catalogue (Alur et al) and applied them to Flex RIA development and Flex/J2EE integration.  From the questions you're asking, Cairngorm is going to be instantly familiar to you, and will get you rapidly up to speed with organising and architecting a Flex RIA.
 
When you download Cairngorm, there's also a "Cairngorm Store" application, that will be a good starting point for you for seeing how the framework is used in anger.
 
Think mini-Struts for Flex RIA, and you're there.
 
* What is the best practice to communicate with J2EE application like  
  should I opt for remoteobject or httpService or webService. 
 
For a J2EE application where you own the server-side as well as the client, I'd go RemoteObject every single time, from a performance standpoint, as well as from the stadndpoint of how little (ie not at all) you need to impact your server-side development to accomodate Flex.
 
It's pre-Flex, but I wrote a whitepaper for Macromedia some time ago, to discuss Flash Remoting (AMF / RemoteObject) versus WebService versus HTTPService - you can find it here:
 
http://www.macromedia.com/devnet/flash/articles/ria_dataservices.html
 
I think most of the arguments (if not all of them) still stand.
 
 
* Any recommendation on good books for Flex intergration to J2EE. 
 
Funny you should ask that :-)
 
I'm one of the authors of "Developing Rich Clients with Macromedia Flex", and there's a significant treatment of integration with J2EE infrastructure.  You can find out more at http://www.iterationtwo.com/flexbook/
 
There's a number of chapters of the book available for free download.
 
For you, I'd recommend you start with the chapter on "Flex and J2EE Integration" which was made available some time ago at theserverside:
 
http://www.theserverside.com/articles/article.tss?l=Flex
 
Three other chapters are available at macromedia.com:
 
http://www.macromedia.com/devnet/flex/articles/behavior_effects.html
http://www.macromedia.com/devnet/flex/articles/component_reuse.html
http://www.macromedia.com/devnet/flex/articles/data_binding.html 
 
I think that's MORE than enough resource to get you started.  If you have any further questions on Flex/J2EE integration, or on the Cairngorm microarchitecture for RIA development, please don't hesitate to ask.
 
It's a leap of faith from a previous life of abusing stateless HTTP protocols to produce anaemic and ineffective user experiences, to the brave new world of developing richer, more immersive and effective RIA user experiences with Flex. 
 
Welcome to the other side.
 
Steven
 
--
Steven Webster
Technical Director
iteration::two
 
This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies of it, immediately.
 
Please also note that while software systems have been used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened.
 



--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




YAHOO! GROUPS LINKS




Reply via email to