Hi, In your forwarder.jsp file you access an attribute TEMPLATE_PATH in the session. This I assume was set in the browse.action that just executed. The problem is that since you have a frameset, several browse actions are executing at the same time and they all try to write this same variable in the session. The session is the same in all the frames so therefore they overwrite the TEMPLATE_PATH variable which produces the "random" results you get.
I think that the reason that you do not get the error the first time that you access the frameset, is that then you do not have a session at all. You have not used the url tag for the SRC attribute for the frames, so you do not get any session id encoded in the SRC url. Since it is the first request you do not have a cookie on the client either, so each frame will actually have a separate session the first time. When you hit F5 you already have a session cookie in your client so then the session in each frame will be the same, and therefore you get the error at that point. At least I think that is what happens! Why dont you let your forwarder.jsp access a getTemplatePath property in the browse.action instead of storing it in the session? Cheers, Dick Zetterberg [EMAIL PROTECTED] ----- Original Message ----- From: "Robert Douglass" <[EMAIL PROTECTED]> Subject: [OS-webwork] Bug with frames > I'm experiencing a weird bug in my frameset. When I reload, there is about a > 30% chance that the frames will load their neighbors URL. I suspect it has > something to do with the way I'm managing navigation in general, and > specifically a threadsafe problem. However, I'm not sure, and therefore > sharing the likely suspects with everyone here. First, the frameset: > > <FRAMESET rows="0, 8%, *"> > <FRAME name="invisible" border="0"> > <FRAME name="ControlFrame" > SRC="browse.action?template=ControlFrame&id=<ww:property > value="model.id"/>"> > <FRAMESET name="ContentFrameset" cols="15%, 0%, *, 0%"> > <FRAME name="NavFrame" SRC="browse.action?template=NavFrame&id=<ww:property > value="model.id"/>" border="1"> > <FRAME name="EditFrameFormView" > SRC="browse.action?template=EditFrameFormView&id=<ww:property > value="model.id"/>" border="0"> > <FRAME name="EditFrameLayoutView" > SRC="browse.action?template=EditFrameLayoutView&id=<ww:property > value="model.id"/>" border="0"> > <FRAME name="PreviewFrame" > SRC="browse.action?template=PreviewFrame&id=<ww:property value="model.id"/>" > border="0"> > </FRAMESET> > </FRAMESET> > > browse.action receives template and id as parameters. It looks up a data > object based on id, and looks up a jsp file based on template. > Browse.success = forwarder.jsp, which has one line: <jsp:forward page='<%= > (String) session.getAttribute(TEMPLATE_PATH) %>' /> (I've recently detailed > this in another thread, excuse the redundancy) > > The page always loads correctly the first time. Only F5 creates problems. > There are five SRCs in the frameset. That leads to five requests. It appears > that request 1 is getting request 2's forward etc. Furthermore, the actual > result of the bug is unpredictable. Requests 2, 3 and 4 can all get 5's URL > and so forth. Any ideas? > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
