This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
JSF is not a jealous platform. If you have something that needs doing that doesn't benefit from JSF, don't ram it through JSF. A classic example of that is when people want to produce PDF or spreadsheet documents. I'm constantly cautioning people that a plain old servlet is better for that part of the webapp than hijacking the internals of JSF. Sometimes they even listen to me. :cool:
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Mar 06, 2013
Thank you for your answer.
Of course this is still connected to JSF. But using an extra servlet I do not see the possibility to create validation messages for example as the FacesContext is missing.
However, the primary architectural constraint is that not only JSF, but HTTP itself requires a form. While you could issue a straight HTTP GET request via AJAX without a form, that doesn't give the benefits that a full JSF form postback would.