Hi, my question was probably unclear, I will try to post more details:
When I leave a page, let's say id=40, wicket gets request to render new page id=41 but flash on previous page still lives and send request to wicket (this is the souce of troubles). This request from flash is bound to page id = 40 and causes wicket to think, that user pressed back button on the page id=41, so the page id=41 is removed from accessStack. Browser then renders page id = 41 and send requests for components like pictures etc, but since page id=41 was removed, all requests return "session expired". How can I fix this problem? (wicket 1.2.6) Many thanks, Jan -- Jan Bares http://jan.vegetband.cz "jan_bar" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi, > > I have some troubles with Wicket 1.2.6. I have two pages, pageA has > Image(s), pageB has Flash that talks back to wicket. Here is a trace of HTTP > requests: > > pageA - HTML is sent to client > page.image(s) - images are send to client > pageB - HTML is sent to client > pageB.flash - flash starts it's background requests > pageA - now I switch back to pageA via pageB.Link > pageB.flash - flash on pageB still lives and sends request to wicket, this > is the source of trouble > pageA.images - images on pageA doesn't exist, because "session expired" > > The trouble is that Flash still "lives" even when new page is loaded into > client. The request from flash seems to confuse wicket. How can I fix this > problem? > > Thanks, Jan > > -- > Jan Bares > http://jan.vegetband.cz > > > > > > --------------------------------------------------------------------- > 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]
