I've done some pretty extensive troubleshooting, but will try and expand on it. The product is a generated and delivered (as a pdf) right after the user clicks on the Confirm button. I thought that the use of an interceptor for this purpose was ideal, but I'm a Struts novice and far from an expert Java programmer. Can you explain why the use of an interceptor is not the right way to go about this? Thanks!
newton.dave wrote: > > --- daveck <[EMAIL PROTECTED]> wrote: >> Sometimes "PARMS" manages to keep its value, and sometimes >> the value disappear. > > I don't see anything immediately obvious; IIRC you had already checked the > session ID to make sure you were always dealing with the same session, > correct? Have you done extensive logging / tracing / etc. to make sure the > value of "PARMS" in the session is getting set *only* when you believe it > should be (this is what I would be most suspicious of first)? > > That said, I'm pretty uncomfortable with this use of an interceptor: is > this > functionality really required across broad swaths of your application? Is > the > order not stored in some application-specific object that could be stored > in > the session (or somewhere else) then retrieved again in a confirmation > action? > > Dave > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Need-help-with-Struts-Interceptor-session-problem.-tp15598155p15599632.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
