This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
If I do this, then any attempts to reach Process.jsp have to go through the Process servlet first. I know the concept is pretty basic, but I was just wondering if I should be doing this a different way, or if there was a reason I wouldn't want to do it like this. Thanks... [ May 03, 2005: Message edited by: Stephen Huey ]
My intention was to never post to the JSP directly...so if I have a post from Process.jsp, I would always post to the Process servlet, and the Process servlet would always eventually forward to the JSP (and any GET requests would also go through the servlet in the same fashion). That's why I mapped the URL Process.jsp to the Process servlet--so that the JSP wouldn't typically be invoked directly and also because I wanted /Process.jsp to show up in the address bar and not /Process alone.
But if it's better not to do this, then I can just change it so that /Process is the last thing in the URL in the address bar.
if your problem is to have in the address bar Process.jsp, well...the url-mapping can be WHATEVER you want, you can put in the url-mapping FooFooFoo.jsp and still have the servlet Process executed, additionally, if you want your servlet to forward the request, you simply have to write inside the code of the servlet something like : RequestDispatcher view = request.getRequestDispatcher("result.jsp");