CORBA!
Phil McGlauchlin
Senior Systems Engineer
Inprise Corporation
[EMAIL PROTECTED]
630-955-3730
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Eric Yu
> Sent: Wednesday, September 15, 1999 11:12 AM
> To: [EMAIL PROTECTED]
> Subject: JNI from EJB 1.1
>
>
> In Sun's draft EJB developer's guide (and also probably specified
> somewhere
> in the EJB 1.1 spec), it lists among the Programming Restrictions:
>
> ----
> When coded properly, an enterprise bean will run in any EJB-compliant
> container. To be portable, an enterprise bean is restricted from
> performing
> certain operations:
>
> accessing files or directories with the java.io package
> managing or synchronizing threads
> using AWT functionality to display information or to accept
> information
> from a keyboard
> listening on a socket, accepting connections on a socket, or using a
> socket for multicast
> setting a socket factory used by ServerSocket, Socket, or the stream
> handler factory used by the URL class
> loading a native library
> ----
>
> The last one implies JNI from within an EJB is prohibited. What would be
> some strategies to access native libraries from an EJB?
>
> Thanks,
>
> Eric Yu
> Centerprise Services, Inc.
> (914) 701-7320 voice
> (914) 701-7391 fax
> mailto:[EMAIL PROTECTED]
>
> ==================================================================
> =========
> 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".
