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 has absolutely no database capabilities at all, so that means that you have to supply your own code to do the storing.
Beyond that, something has to invoke that code.
When you provide a SUBMIT button, whether traditional or AJAX it has to be attached to that code. For traditional submits, that would be an action method or (not recommended) action listener. For an AJAX button, you'd attach an AJAX listener method.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Nov 15, 2012
I have sorted at the moment wit the action attribute in the commandButton that references to a method
in the managed bean whose body holds the facade object and the create method and return a new response page.
I think I need to become clearer about the navigation in J.S.F.
An AJAX request will not navigate. It is used for updating the current page.
A traditional JSF action method will navigate. It returns a rule name that is used to select which page to display next. If it returns null, the same page is re-displayed. In JSF2, explicit rule names are optional. If the returned value is not an explicitly-defined rule name, JSF will attempt to make a URL out of it and navigate to the page that corresponds to that URL. Being JSF, the URL in the browser location control will lag behind, but that doesn't matter for the purposes of navigation. A "redirect" option can be used in cases where you want to update the browser control, although there is a performance penalty involved.