When you’re developing a JSF or ADF Faces application and your giving your customer a first testing-experience, you’ll notice the browser’s back button is a very interesting functionality used by a lot of end-users.
JSF saves the state of every page loaded in a browser, which means everytime a user clicks the browser back button, JSF loads the saved state of the target page.
You will also notice that the application is behaving very weard and unpredictable and you as a developer will need to solve the problem.
- Integrate the needed java script functionality to display the application in a full screen window (back button isn’t displayed anymore)
- Define no-caching on your web application using the phaselistener (jsf api’s)
- The user needs to refresh the page he ‘backed to’ => maybe this isn’t an option when I’m talking about developers and customers ;o)
- Use ‘enableTokenValidation=false’ within an ADF Application
- Define the needed state- and session-parameters in your jsf’s configuration file, read following post
I still think, when talking to collegues, browsing the internet/communities etc., you need to tell the customer that when using the back button, unexpected behaviour can occure in the application. Using bread-crumbs, task-oriented applications, separate crud-pages, etc. the customer won’t be that easily temped to use the back-button.