LoadLibrary冻结(LoadLibrary freezes)

 您应该始终通过URL重写来创建URL，不仅可以将会话信息添加到URL（如果需要），还可以添加上下文路径。 您应该从应用程序顶部创建所有URL作为绝对路径，然后让URL重写句柄，根据需要将context-path添加到前面。 
 
<c:url value="/css/site.css"/>
 
 如果他们没有启用cookie，那么会将/&lt;context-path&gt;/css/site.css或/&lt;context-path&gt;/css/site.css;jsessionid=134345434543呈现到jsp文件中。 您还可以使用c：url标记将url呈现为​​变量，然后在整个文档中多次使用该变量。 只需在标记中添加var="x"属性，然后${x}就会将网址呈现到您的文档中。 如果您没有使用jsp来渲染输出，则需要为视图层找到适当的机制，但它们都有一个。 如果你在java代码中渲染一个url，只需看看c：url标记的源代码，你就会看到它是如何完成的。 
 
 一个尴尬是CSS文件（和js文件）没有被处理，因此css和js文件中的url需要是相对路径，否则每当你更改上下文路径时它们都会中断。 大多数js已经使用了相对路径，因为库维护者不知道你要将库安装到哪个路径。 另一方面，CSS背景图像通常被指定为绝对URL，因为相同的CSS文件可以包含在文件层次结构的不同级别的html文件中。 除了创建适当的符号链接以使相对URL始终有效或者通过JSP提供问题CSS文件以便可以适当地重写URL时，我没有简单的解决方法。 我确定你可以运行的过滤器或apache模块可以进行url替换，但是当你部署到新的上下文路径时，你仍然需要手动更新过滤器/模块。 

You should always create urls via url re-writing, not only so that session info can be added to the url, if required, but also so that the context path can be added. You should create all urls as absolutely paths from the top of the application and then let url-rewriting handle adding the context-path to the front, as appropriate.
 
<c:url value="/css/site.css"/>
 
That will render /&lt;context-path&gt;/css/site.css or /&lt;context-path&gt;/css/site.css;jsessionid=134345434543 into a jsp file if they don't have cookies enabled. You can also use the c:url tag to render the url into a variable and then use that variable multiple times throughout your document. Just add a var="x" attribute to the tag and then ${x} will render the url into your doc. If you aren't using jsp to render your output, you'll need to find the appropriate mechanism for your view layer, but they will all have one. If you are rendering a url in java code, just take a look at the source code to the c:url tag and you'll see how it is done.
 
The one awkwardness is that CSS files (and js files) aren't processed, so urls in css and js files need to be relative paths or they will break whenever you change the context path. Most js already uses relative paths since library maintainers don't know what path you are going to install their library to. CSS backround images, on the other hand, are often specified as absolute urls, since the same CSS file may be included into html files at different levels of a file hierarchy. There is no easy fix for this that I am aware of other than to create appropriate symlinks such that the relative url always works or else serve up the problem CSS files via a JSP so that the urls can be rewritten as appropriate. I'm sure there are probably filters or apache modules you can run which will do the url replacement, but then you've still got to manually update your filter/module whenever you deploy to a new context path.