• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JSF and The FrontController Pattern

 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi everyone,

I'm just looking into JSF to see how well it will fit into the kind of applications that I'm doing. I'm currently using an implementation of the FrontController Pattern with Helpers and Commands (http://java.sun.com/blueprints/corej2eepatterns/Patterns/FrontController.html) to manage the Model and View of my applications.

My question: Is there any need for a FrontController+Helpers+Commands when using JSF? It seems like it will just be two the amount of code to manage. Is JSF a mature enough solution to replace a well implemented FrontController?

Thanks.

Kind regards,
Allan
 
Ranch Hand
Posts: 15304
6
Mac OS X IntelliJ IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JSF uses a Front Controller. There is a FacesServlet that controlls every request sent to it. The difference between what you are currently using and what JSF provides is a component framework. There are many discussions in this forum on that very topic if you just do a search.

As far as replacing what you currently have, JSF is not mature. It is very new. But it is very stable and works very well. There are some bugs and features missing from the current implementation but you can say that about any framework no matter how long it's been around. With that being said, unless you see a significant reason to replace what you have, especially if what you have is currently working and serving its purpose, then I'd think long and hard about the conversion process and what, if anything, you would gain from reworking the application. If it ain't broke...
 
A wop bop a lu bob a womp bam boom. Tutti frutti ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic