A way to do it is to have a class with static methods that do the JNI
access.
This way, if your EJB gets replicated to another VM that same class might
have been instantiated with different parameters and you can now access it
from the same EJB
Filip
Filip Hanik
Engineering Manager/Architect
XMarkstheSpot
[EMAIL PROTECTED]
Come for the cash, stay for the convenience @ http://www.XMarkstheSpot.com
Jon Dart
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
Sent by: A cc:
mailing list for Subject: Re: EJB and JNI
Enterprise
JavaBeans
development
<EJB-INTEREST@jav
a.sun.com>
03/28/00 11:48 AM
Please respond to
A mailing list
for Enterprise
JavaBeans
development
>Date: Mon, 27 Mar 2000 16:24:16 -0800
>From: Tony Holderith <[EMAIL PROTECTED]>
>Subject: Re: EJB and JNI
>MIME-Version: 1.0
>Content-Type: text/plain; charset=iso-8859-1
>X-MIME-Autoconverted: from 8bit to quoted-printable by osgood.tibco.com id
BAA06481
>
>
>There should be a 'safe' way to allow (certify) an EJB to use JNI. This
>is a relatively common need.
>
>
>Tony
>----
>
If you've got a Java 2-based server, then the ability to load native
libraries
is controlled by the server's security policy file. You can go edit this
and allow the loading to occur. It might not be safe, or portable, but
you should be able to do it.
--Jon
-------------------------------------------------------------------
Jon Dart [EMAIL PROTECTED]
TIBCO Software Inc. 650-846-5099
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
