Rickard,
Please clarify. Should not or CAN not load the JDBC driver? If I'm using
BMP, why not let the session bean load the driver? What repercussions are
there from a session bean doing that (and assuming there are no entity beans
in my application)? Is EJB connection pooling by the container compromised
in this situation?
-Ron
> (assuming EJB1.1)
> Let's be very specific here. No, your session should not load the JDBC
> driver, since you should acquire it (through a DataSource) from JNDI.
>
> That said, to really answer what I think you're asking (might be totally
> off here, let me know):
> You are correct that the JDBC driver will be loaded by the EJB servers
> classloader, even though the bean is making the actual use of the class.
> This is standard ClassLoader-behavior: the topmost classloader that can
> access a class with a given name will do so.
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> Homepage: http://www-und.ida.liu.se/~ricob684
>
> ==================================================================
> =========
> 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".
