Wen launching webapp B (from A), you can pass jsessionid as url parameter (not as jsessionid) to B; with this jsessionid you can call A from B for keep-alive.
Gernot -----Ursprüngliche Nachricht----- Von: Patrick Lacson [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 13. Mai 2005 06:57 An: Tomcat Users List Betreff: Re: Sessions and keep-alives I've considered iframes, but unfortunately not an option for us. >From what I understand AJAX can make async calls to the HTTP server from the webapplication only, not on behalf of another. So if the popup application is webapp B, and the parent webapp A, how can I call the webapp A server from webapp B for the keep-alive? On 5/12/05, Tim Funk <[EMAIL PROTECTED]> wrote: > The simplest kludge is an iframe that is "hidden" and uses a META refresh. > > Or look at using ajax. > > -Tim > > Patrick Lacson wrote: > > > hi All! > > > > I'm involved in a project that integrates two disparate web > > applications: webapp A is using WebSphere and webapp B is using > > Tomcat. > > > > The integration involves Single Sign On, with webapp A being the > > primary webapp from which webapp B is launched. webapp B is launched > > as a popup-window. > > > > My question is: how can i ensure that while the user is working on the > > webapp B popup, the parent window webapp A, does not time-out? > > > > Thanks in advance! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Patrick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
