This can be done in several ways. I think this way is the most straightforward: Move the WAR file outside of the webapps/ auto-deploy directory Extract META-INF/context.xml from your WAR file. If your WAR doesn’t have a META-INF/context.xml file, just use a file with nothing but <Context /> in it Copy this file into Tomcat’s … Read more
URLs are not resolved based on the file structure in the server side. URLs are resolved based on the real public web addresses of the resources in question. It’s namely the webbrowser who has got to invoke them, not the webserver. There are several ways to soften the pain: JSF EL offers a shorthand to … Read more
If your actual concern is the dynamicness of the webapp context (the “AppName” part), then just retrieve it dynamically by HttpServletRequest#getContextPath(). <head> <link rel=”stylesheet” href=”https://stackoverflow.com/questions/4764405/${pageContext.request.contextPath}/templates/style/main.css” /> <script src=”${pageContext.request.contextPath}/templates/js/main.js”></script> <script>var base = “${pageContext.request.contextPath}”;</script> </head> <body> <a href=”${pageContext.request.contextPath}/pages/foo.jsp”>link</a> </body> If you want to set a base path for all relative links so that you don’t need to … Read more
Before deciding whether to use the <base> tag or not, you need to understand how it works, what it can be used for and what the implications are and finally outweigh the advantages/disadvantages. The <base> tag mainly eases creating relative links in templating languages as you don’t need to worry about the current context in … Read more