Not a patch, but a workaround is to maybe subclass the templatelink that you
are using.. I think called JSPTemplateLink? and have it automatically do the
addPathInfo("non","sense") stuff for you.. reduce the pain a bit!
Eric
-----Original Message-----
From: Alexander Banthien [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 18, 2002 11:19 AM
To: Turbine Users List
Subject: Re: access to JSP templates through turbine
Hi once more,
now after updating my tomcat to 3.2.4, I still have the problem. If anybody
knows how
to work around it and tweak tomcat 3.2.x to take the proper decision wether
to run a
servlet or run a straight jsp, please let me know.
In the time time being, there is the following workaround:
code your links like this:
<a href="<%=
link.setPage("something.jsp").addPathInfo("non","sense")%>">..</a>
resulting in a url:
http://myserver.my.net/app/servlet/app/template/something.jsp/non/sense
which is not recognized as the URL of a jsp by the servlet container. The
servlet is
run properly, is dispatches the request to the correct jsp page. The extra
info in the
path is obviously disregarded.
Not nice (especially the <%= %> ugliness), but it works.
And of course, if anybody knows the proper way through this problem, I am
glad to hear
about it :-)
regards again
Alexander Banthien
_______________________________________
Questech GmbH
Schwarzwaldstr. 19
79199 Kirchzarten
Fon: +49 (0)7661 90 35-15
Fax: +49 (0)7661 90 35-20
www.questech.de
_______________________________________
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
