Leon Rosenberg wrote: > first, if you are new to servlets and webapps, you should probably > hire a consultant in your area to help you out a little, and there are > many in germany. > > second, you don't need own session handling, what you do need is a > context for each window in your session, so the data for the window is > set in the context. This implies that you have somehow to identify in > which context a window is. The standard way of doing it with cookie, > doesn't work for you (either way you'd had no problems with sessions), > so the easiest way is to append a context id to each relevant link in > the window. This can be done manually, if the link count is low, or > via a own HttpServletRequest wrapper with encoding methods, or (but > really ugly) by a filter which rewrites the response afterwards. > I would highly recommend you to add the context id manually to each > link in the window; its maybe more work at the beginning and not > fancy, but it will work and be fault tolerant. > > So once you did that, you have a map with contextId-contextdata > relationship in the session, retrieve the proper contextdata from the > session in a filter and add it as request attribute, work with it in > servlets/actions whatever and use the proper context id in the links. > You could also make the context object ThreadLocal, and spare > HttpServletRequest passing through methods. > > Pretty simple actually.
They might just need to use request attributes or parameters, which would be even simpler... p > regards > Leon > > > On 9/12/07, Preuss, Jacqueline - ENCOWAY <[EMAIL PROTECTED]> wrote: >> Hi, I'm new here! >> >> >> >> Generally, I'm new in the topic servlets etc. so I hope I can explain my >> problem well. >> >> >> >> In our company we work with some web applications running in Internet >> Explorer. We want to use Tomcat as servlet engine / webserver. The problem >> is the session handling of Tomcat. For the application the user >> authenticates with username, password and domain (i.e. windows >> authentication). The user can select different items in the application e.g. >> quotes. Every quote is opened in a new browser window. If we use Tomcat, all >> quotes of the user are saved under the same session, i.e. the session id is >> always the same. That's a problem for us, because we need a new session for >> every single quote. So, is there a possibility to implement our own session >> handling for Tomcat. If yes, how? What would you suggest? Can we use a >> filter for tomcat the renew or clear the session? >> >> >> >> I hope this is the right place to post. Thanks for help. >> >> >> >> >> Jacqueline Preuß >> >> >> >> > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
