File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes JSF and the fly likes Securing data at end of app Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Java » JSF
Reply Bookmark "Securing data at end of app" Watch "Securing data at end of app" New topic
Author

Securing data at end of app

Salvatore Donnarummo
Greenhorn

Joined: Jul 24, 2008
Posts: 1
Hey guys,

A general summary of the app I'm building:
Users are presented with a series of pages where there input is taken and stored in a session bean. A verification page is displayed to them with all of their information displayed so that they can confirm ro make any corrections if necessary. When they click submit, the data is sent to a db and a confirmation number is returned on a confirmation page.

So my issue here is after the user submits their data to the db and the confirmation page is displayed, I need a few things to happen:
1. I provide a link which will redirect to another page that needs to display the information along wtih confirmation number in a printer friendly format
2. If the user navigates to any other page, ideally the data would be eliminated from the session
3. I need to remove the recently submitted data from appearing in the earlier pages if the user manually navigates back to a previous page by typing in the url (back button on the browser has been disabled) or attempting to submit another set of data

Is there a way to keep the information in the app to be displayed in the printer page, and still remove the information in the current session bean?

I was debating on creating a copy of the current session bean, and storing it as another instance that would be accessed by the printer page while removing the original from the context. It solves the problem of having the data appear in the previous screens, but that still leaves the issue of the data being stored in the session.

Any ideas are appreciated.
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: Securing data at end of app
 
Similar Threads
refreshing a form with bean values when returning to jsp
Carry values between page submit
moving values from 1 select box to another
Distinction between Stateful and Standard session bean.
DispatchAction question