That is the desired behavior of a session bean -- one instance for the user's session. If you want to use session, and have it be able to be cleared, then you will want to create a clear action or action listener method that clears all of the member variables when executed.
I would instead recommend using conversational scope from JBoss-Seam or MyFaces or request scope and use saveState as needed to persist values across pages. -Andrew On 6/13/07, bansi <[EMAIL PROTECTED]> wrote:
We have backing bean defined in "session" scope So whenever we do a submit on JSF Form, it holds onto same backing bean. This is not desirable as -> The Form will have different set of values each time it does a submit -> The Backing bean has variable defined to instantiate a POJO i.e.private MyPojo pojo = new MyPojo(); So every time JSF form submits to the backing bean, it holds onto the same instance of POJO which eventually results in insertion problems into database i.e. having same Identifier (ID) value -> The same problem occurs if i navigate to different page and come back to original page Is their a way to re-initialize the Backing Bean ??? -- View this message in context: http://www.nabble.com/How-to-Re-Initialize-JSF-Backing-Bean-on-Form-Submit-tf3918359.html#a11110517 Sent from the MyFaces - Users mailing list archive at Nabble.com.
