Hey
Ron Yust wrote:
> Please clarify. Should not or CAN not load the JDBC driver?
Should not. I wont say why it can do this again, because I've said why
enough times now.
> If I'm using
> BMP, why not let the session bean load the driver?
This is a weird question as BMP relates to EntityBeans and not
SessionBeans. Both EB's and SB's should acquire JDBC connections from
DataSources acquired through the JNDI namespace "jndi:comp/env/jdbc", as
stated in the EJB1.1 specification.
> What repercussions are
> there from a session bean doing that (and assuming there are no entity beans
> in my application)?
None. It's just pointless, since there is a given way to do this in the
EJB1.1 specification.
> Is EJB connection pooling by the container compromised
> in this situation?
It can be, yes. It could definitely compromise the containers ability to
maintain transactional integrity as it has no way to intercept and
register the connections with the tx.
In short, do as it says in the EJB1.1 specification.
/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".
