Thanks Kevin
but that's not quite what I'm getting at. Let's see if I can clarify:
1. semantics re:forward/back
Yes, I am *forwarding* BACK to StepA.jsp which knows to grab the bean from
the session
and any errors from the request.
2. URL displayed on browser command line
No, this is not a concern at all.
3. the problem is - how does the controller know which JSP a request came
from?
We know what URL we are POSTing to but not where the POST is coming from.
As I indicated you can use the REFERER header to get this information BUT
this header
changes from "StepA.jsp" to "StepA.do" viz:
a. StepA.jsp submits to StepA.do: REFERER = /StepA.jsp
b. controller detects bad data as per previous email and
uses RequestDispatcher.forward( "/StepA.jsp" ) to go back
c. HOWEVER the URL now says StepA.do and when user resubmits the REFERER
header=/StepA.do
d. if there is still bad data controller attempts to
RequestDispatcher.forward( "/StepA.do" )
which is wrong and causes a endless loop
Note: I cannot assume StepA.do was POSTed to by StepA.jsp since there could
be StepA_French.jsp or StepA_shortform.jsp i.e. multiple views for one
action/model
Hope this helps
Thanks again
@
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
