Andy,
Forgive me if I'm insulting your intelligence by mentioning this. I discovered
while using Tomcat that I had to distingush URL paths used in jsp:include tags
(RequestDispatcher.include() calls) and jsp:forward tags
(RequestDispatcher.forward() calls) from URL paths used in generated HTML
pages. The former were being interpreted relative to the servlet context,
whereas the latter were not. Therefore a "/" in a generated HTML page ends up
being interpreted relative to server root.
Troy
[EMAIL PROTECTED] wrote:
> Thank you very much for the response. I agree with you but for some reason
> it is interpreting the slash as the server document root. It only seems to
> do this in one section of my application. Here's the scenario. There is a
> point in my application where the user selects the product they wish to
> order from a list that is presented to them. This list is an ordinary JSP
> page inside the main browser window. However, once they select this
> product by clicking on a link, it invokes a small pop-up window which
> requests that they enter a quantity. Once they enter the quantity and
> click proceed, the child window closes and returns control to the parent
> window. The parent window then submits it's form to a servlet which adds
> the new line to the order. This servlet then redirects the user to a jsp
> page to display the new line. Inside that servlet and the JSP page it
> presents, all links and redirects that contain the '/' attempt to send you
> to the server document root. It seems that whatever is called in relation
> to the child window that was invoked attempts to reference the '/' as the
> server document root. I hope this could provide some direction into this
> issue.
>
> Thanks again,
> Andy
