>Okay, as usual, orion support is so crappy that I got a response and a
>correction within about ten minutes. :)
how do you access that support line ($?)?
>The solution is simple: in the form that failed, the action was
>"testSrv" where that servlet name was mapped. The problem was that when
>you have a URI like this, it gets a browser redirection, which causes the
>GET. The fix is simple: use "testSrv/" instead of "testSrv", which doesn't
>require a redirection.
Now, I really would like to know why an URI like this "gets a browser
redirection". And also, I dont think the fix is all that simple - after all
it requires me to change all my JSP files before deploying to orion. I
already have them running under Tomcat 3.1 and Resin 1.1.
And, since wer'e at it, heres another one: I have a JSP page in my
application that gets invoked from the servlet through the following code:
String url="/jsp/Checkout.jsp";
ServletContext sc = getServletContext();
RequestDispatcher rd = sc.getRequestDispatcher(url);
rd.forward(req,res);
On that page is a link with the following syntax:
<ahref="jsp/EShop.jsp">bla</a>. When I run this within
Tomcat/Resin, the browser (IE5) resolves this to
"http://server/application/jsp/Eshop.jsp".
Under Orion, it becomes
"http://server/application/servletPath/jsp/Eshop.jsp", which is broken. The
generated page source is identical, so its the browser that gets mixed up.
What is wrong here? What determines how the browser interprets a relative
link?
>Basically, the particular form of the uri mapping
>for the servlet name was causing the problem.
hm, I dont mean to be picky, but isnt some software at least also involved
in this? To me it looks like this is inconsistent behavior between
Tomcat/Resin and Orion, which IMHO should ideally not exist...
Christian
