You should not use JNI inside an EJB.
See Section 18.1.2 of the EJB spec, on programming restrictions.
An extract below.
<Quote>
� The enterprise bean must not attempt to load a native library.
This function is reserved for the EJB Container. Allowing the enterprise
bean to load native code would create a security hole.
</Quote>
-- Aravind
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ulrich Kriegel
> Sent: Monday, 27 March 2000 18:55
> To: [EMAIL PROTECTED]
> Subject: EJB and JNI
>
>
> Hi there,
> we will encapsulate an C++ calculation module as an EJB. Exists any
> exprience about the performance of EJBs using JNI to delegate work to
> C++-modules. What about the status of an C++-module in case the
> container moves the EJB to secondary store?
> --
> Thanks
> --ukriegel
> ---------------------------------------------------------------------
> Dr. E.Ulrich Kriegel, [EMAIL PROTECTED],
> Fraunhofer ISST, Mollstra�e 1, D-10178 Berlin, Germany
> tel: (++49(0)30) 243 06 446 fax: (++49 (0) 30) 24306 199.
> For public key either send mail with subject ##public-key or look at
> http://www.isst.fhg.de/~ukriegel/public-key.html
> =====================================================================
>
> ==================================================================
> =========
> 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".
