How about this, then?
<%
String codebase = request.getScheme() + "://" +
request.getServerName()
+ ":" + request.getServerPort() + request.getContextPath();
String href = request.getServletPath();
%>
This is also more efficient than parsing the string yourself (since
the
HttpServlet has already done that work for you).
Yes, you have reason :-) ... anyway I'm thinking to refactor some of
the common code from this page in one or more fragments, to reuse them
by including in other pages ...
Seems like that might be over-designed. I would suggest keeping it
simple for now and seeing how it goes.
2) We might want to consider mapping the "jnlp" extension to the
JSP
servlet
so we can just call this file "kitchen_sink.jnlp".
One question: changing the Application Server I could not be able to
run jsp pages (I could have no more Tomcat JSP classes available),
it
is Ok ?
So I don't like too much this, but i can try to do the trick.
This shouldn't require making changes to the application server -
mapping an
extension to a servlet is done in web.xml, as I recall.
Ok, but I fear if i have to map this extension to a Servlet (the JSP
Compiler) that could not exist on others applications server ...
I had assumed that there was a way to do this in an app server-
independent way...anyone else have any insight?
