We've encountered a situation with the latest TomCat 4.1.12 where a consultant hardcoded jsp pages pointing to the old directory and I was wandering which of these routes to go:
a) The jsp files look to be hard coded with directory listings which do not include the port 8080 configurations. Solution would be to set this hardcoded directory as a variable in an include file. b) Somewhere in the TomCat configuration, should be a way to re-direct the connection to the new directory location of the new TomCat. Does anyone out there / Has anyone encountered this situation? If so could you answer (b) for me on how to do this? TIA, Keith E. Kosmicki Applications Consultant State of IL Human Services STL Technology Partners ==========================================================================To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
