Should i learn jsf

Ask Question. Asked 11 years, 6 months ago. Active 7 years, 7 months ago. Viewed 28k times. Below are the quote from the above tutorial: Servlet are best suited for service-oriented App and control function of presentation-oriented App like dispatching request JSF and Facelet are more appropriated for generating mark-up like XHTML, and generally used for presentation-oriented App Not sure if I understand the above quote too well, they did not explain too well what is service-oriented vs presentation-oriented.

Improve this question. BalusC 1. Thang Pham Thang Pham Add a comment. Active Oldest Votes. Improve this answer. Community Bot 1 1 1 silver badge. BalusC BalusC 1.

Srry I should have look before I posted. Will definitely read your post. But from what I am reading now. Am I right? JSF provides the FacesServlet yes, it's a servlet! They are indeed competitors.

Note that "Spring"! Harry: balusc. Show 3 more comments. The reason I like JSF is that you can access good quality components that are mature and well-documented. It also has the advantage of allowing teams that are weak on frontend skills to develop professional looking websites. The JSF model has fallen out of favor. This approach can often scale better than JSF. The StackOverflow blog post shows it's not all plain sailing in the frontend JavaScript world.

The frameworks suffer from relatively short lifespans, and although there are migration strategies, you do run the risk of your javascript framework being obsolete. JSF has the advantage of being a mature model in this respect. It's also worth remembering that if your team is lacking in frontend skills, then JSF will help you quickly deliver a professional-looking website.

See the original article here. Thanks for visiting DZone today,. Edit Profile. Sign Out View Profile. It's cumbersome a complete waste of resources and CPU power. Tim Holloway. Saloon Keeper. JSF is a good thing to know if you need to design an industrial-grade webapp with lots of user input and validation, although I've never been sure that its overhead is low enough to run something the size of Amazon.

Java in general is expensive to implement, since apps cannot be just slapped out in an afternoon. For lightweight stuff, I usually use PHP or node. Note that many extensions to JSF use jQuery internally, but usually with less coding required they also usually allow direct use of jQuery also.

One thing to bear in mind, however, is that while some things benefit from being offloaded onto the client, anything to do with data validation should ultimately be done on the server. That's simply because anything done on the client can be hacked or spoofed. It does no good to have client-side code validating data if some ill-intentioned person takes over and pushes bad data down anyway. Giovanni Murguia. The JSF life cycle make it slow and error prone and it takes plenty of time to learn to get it right.

Another big disadvantage is that, since the framework is trying to abstract the HTTP protocol and HTML code for the most part, you sometimes end up tweaking the framework to fulfill a special requirement.