Hi !
I can think of three ways to achieve this functionality:
1. HTTP Referer
- you can get the referer from the Servlet API, but this will only work if the client has NOT turned off the feature. Some browsers and proxy-servers turn this functionality off by default.
2. sourceId in queryString
- append the sourceId attribute to all the links on the current page and attach sourceId to a URL in the DB
- this works if a user has multiple windows open and is relative with each window
3. sourceId in session
- save the sourceId in a session scoped variable, and update it with each request (using filters)
- however, if the user has multiple windows open, then, only the last request will determine the sourceId
HTH,
Kunal
Prasad, Kamakshya wrote:
Hi All,
We have a web application built on struts. The issue we are having is
implementing a solid navigation framework. All the screens are tightly
coupled to each other. On click of back button it should always go to
the screen which opened it and each screen is getting opened from lot
other screens. But one good point is that each screen is populated by
max 1 or 2 primary keys.
Could anyone please suggest me some framework though which I can handle these i.e. store the chain of actions and also the key for performing that action?
Regards,
KP
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
