>From: Rickard Oberg <[EMAIL PROTECTED]>
>
>On Mon, 6 Nov 2000 11:23:02 -0800, Larry Liu <[EMAIL PROTECTED]> wrote:
> >It is well known statement quoted by your mail. Do you
> >think the move of the IO work to Web tier instead of the
> >EJB tire is the way out?
>
>There is Absolutely Nothing(tm) that prevent you from putting all the file
>I/O into a separate library which your EJB's then access. Period.
>
>Are these classes not covered by the EJB restrictions? No, not if they are
>considered part of the system.
>
>How do I make them part of the system? By installing them in the servers
>classpath, or as an installed extension in the lib/ext directory in the
>JRE/JDK.
>
>So, why does this work? Because the permission restrictions will not apply
>to system loaded classes. For example, the server itself is allowed to do
>file I/O, as do JDBC drivers etc. This would be no different.
>
I can say from experience that WebSphere 3.5 will not allow a JDBC driver
loaded using the system classloader to access the filesystem. WebSphere
throws a security exception when the driver attempts it. The driver is on
the classpath of the VM within which WebSphere is running.
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
===========================================================================
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".
