Eumm.. I recommend you don't call a library from your JSP, but from a
JavaBean (call the bean from your JSP). Also, you may want to read
about how to load a library in Tomcat (see file
${CATALINA_HOME}/RELEASE-NOTES
"
Applications that require native libraries must ensure that the
libraries have
been loaded prior to use. Typically, this is done with a call like:
static {
System.loadLibrary("path-to-library-file");
}
in some class. However, the application must also ensure that the
library is
not loaded more than once. If the above code were placed in a class inside
the web application (i.e. under /WEB-INF/classes or /WEB-INF/lib), and the
application were reloaded, the loadLibrary() call would be attempted a
second
time.
To avoid this problem, place classes that load native libraries outside
of the
web application, and ensure that the loadLibrary() call is executed only
once
during the lifetime of a particular JVM.
"
-- Jeanfrancois
John Murtari wrote:
>We are working with a client who is trying to interface JSP with the
>Chameleon libraries from Interfaceware (www.interfaceware.com).
>
>Interfaceware has recommended using the <page> tag to access this
>library, ie - something like :
> <%@ page import="libchm_java.so">
>but this does not work!
>
>Accessing the Chameleon libs also requires the registration key be
>accessible via an ENV variable. This can be exported to the ENV from
>the tomcat startup script, but then the variables would probably be
>accessible from any of the virtual hosts configured on the machine. I
>had through I could probably defined a <Parameter...> within this
>host's <Context>, but the key contains a & which causes the xml
>parsing of the server.xml file to fail.
>
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
