SF 1662887 protect Dispatch static methods

This commit is contained in:
clay_shooter
2007-02-18 16:11:38 +00:00
parent c63934b4bf
commit fa66c59940
4 changed files with 280 additions and 153 deletions

View File

@@ -10,14 +10,19 @@ Section not yet written.
Jacob.jar relies on a DLL file that it loads off of the library path or classpath.
The code is written so that the jacob.dll is only loaded one time per classloader.
This works fine in the standard application but can cause problems if jacob.jar
is loaded from more than one class loader as in the situation where multiple
jacob dependent web applications run in the same web server.
Jacob is put in the WEB-INF/lib directory of each application's war file.
is loaded from more than one class loader. This can happen in the situation where multiple
jacob dependent web applications run in the same container like a web server or JWS runtime.
<p>
In the case of a web server, Jacob is normally put in the application specific WEB-INF/lib directory.
This is the "right" way to do it and works in most situations.
But, if Jacob is put in the WEB-INF/lib directory of each application's war file for more than
one application then a problem occurs.
In this situation, the web server uses a different classloader for each applicaiton.
This means that each application will attempt to load the jacob.dll and errors
are generated. The only way around this at this time (1.11) is to put the jacob.jar
in the common/lib because that classloader is inherited by all of the applicaitons
so the DLLs will only get loaded once. (This problem is described in SF 1645463)
so the DLLs will only get loaded once. This problem is described in SF 1645463 and
should be fixed in some future release, fix method and time not yet determined.
<p>
<hr>
<h1>Jacob Command Line Settings</h1>
@@ -49,7 +54,7 @@ This library supports several different :
The default is "no additional checking"
Example: -XCheck:jni
Last Modified 10/2005
Last Modified 2/2007
</BODY>
</HTML>