> What Ian really mean to say ;-) was that there is no magic that allows
> JDBC to not abide to the restrictions, but usually the JDBC driver
> (and/or DB) is not packaged with the EJB application, which allows it to
> do I/O (=not the same *CLASSLOADER* as the EJB app! Is it clear now?).
> If the DB is inprocess (as I believe InstantDB is), then the driver/DB
> must use doPrivileged or they'll choke on SecurityExceptions. If they do
> network calls (as most JDBC drivers do), then they're off the hook
> because of that as Permission checks are only done on all callers on the
> stack.
>
> /Rickard
Rickard,
Does this mean my EJB session bean cannot load a JDBC driver like I do in
RMI? The driver class may not be in the same jar as my EJB bean, but it
will be in the classpath for the EJB server. And since there's no other
jvm, I thought the EJB server's classloader would load the driver. What am
I missing?
-Ron
>
===========================================================================
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".
