How to scope beans for a JSF Confirmation Page

Question

I have a web form with corresponding backing bean for each input field. I have two buttons on the form. Here is some of the page:
<h:inputText id="clientName" value="#{clientBean.company}" required="true"/>
<h:inputText id="clientContact" value="#{clientBean.contact}"/>
<h:commandButton id="btn_Submit" value="Submit" action="#clientBean.save}"/>
<h:commandButton id="btn_Cancel" value="Cancel" immediate="true" action="cancel"/>
Navigation rules display a confirmation page with the inputs the user has entered, and the cancel button brings them back to a simple menu screen (where they can click a link and re-visit this web form).
IF THE MANAGED-BEAN-SCOPE for clientBean is set to REQUEST, I cannot use the bean attributes to populate outputText elements on a confirmation page (they are no longer in the current request). (I'm OK with this....)
IF I SET THE MANAGED-BEAN-SCOPE for clientBean to SESSION, I can use the attributes of the managed-bean to drive the confirmation page, HOWEVER... if the user fills in the form and clicks CANCEL, then re-visits the web form, the values they entered prior to clicking Cancel are pre-populated in the web form.
I've even gone as far as to have the Cancel button fire a cancel() method on the clientBean where I set all backing attributes to empty strings. That doesn't work either.
Is there a way I can remove a managed-bean instance from the session scope entirely when the user clicks Cancel? Or is there a preferred method of ensuring that form values make it to the confirmation page using request scoped beans?

Answer 1

I'd the same problem ever.
It's not a good way to do these clear in the cancel button,
for users maybe not click the cancel button, but click others links on the page
and quit, after a while, then goto the form, there will be the previous data
displayed as click back on the confirm page.
at last i resolve the problem by adding a page before the form page.
all links to the form page are linked to the new page,
in the new page,
1st, clear the state of the managed-ben(clientBean),
there were a few ways to do this,
(1), change all the properties of the clientbean to a default value.
(2), remove the clientbean from the session(JSF will create an new instance when it remove from the session)
2nd, redirect the request to the form page.
You may write only one page (the clear-state and forword page) for all form in the application by passing the managed-bean to be cleared as a parameter.
Hope be helpful for you.