aspose file tools*
The moose likes Flex and the fly likes Flex 3 :Is it good to have a FrontController per Module?? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Frameworks » Flex
Bookmark "Flex 3 :Is it good to have a FrontController per Module??" Watch "Flex 3 :Is it good to have a FrontController per Module??" New topic
Author

Flex 3 :Is it good to have a FrontController per Module??

Ravi Kiran Va
Ranch Hand

Joined: Apr 18, 2009
Posts: 2234

Hi ,


Read that there should be a Single Front Controller per application .

But how to manage this as my application is having number of Modules .

Is it good to have a FrontController per Module??

Please share your ideas.

Save India From Corruption - Anna Hazare.
Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

No. Ginven what a FrontController is for why would you do this?

If you are worried about mixing view and business logic there are patterns for seperating these (see Cairgngorm or PureMVC etc. )


JavaRanch FAQ HowToAskQuestionsOnJavaRanch
Joel Hooks
author
Greenhorn

Joined: Feb 17, 2010
Posts: 15
Ravi Kiran V wrote:Hi ,


Read that there should be a Single Front Controller per application .

But how to manage this as my application is having number of Modules .

Is it good to have a FrontController per Module??

Please share your ideas.


In a modular application you generally have a shell. The shell facilitates the communication between modules via interfaces. So when considering modules as independent sub-applications, having a FrontController (this is a Cairngorm approach) for each module with a top-level shell FrontController is a good approach.
 
jQuery in Action, 2nd edition
 
subject: Flex 3 :Is it good to have a FrontController per Module??