> From: Pid [mailto:p...@pidster.com] > Subject: Re: How to turn off JNDI datasource connection pooling > > I'm getting a little confused trying to follow this thread.
There was a distinct lack of specifics in the beginning. However, I think I understand why he's doing this. As Keith mentioned, he's using a legacy DB that likely implements its own access restrictions based on credentials supplied on the connection. Once the connection is established, the credentials cannot be changed. When a new end-user logs in, that user will need a connection specific to that userid. (How do I know this? We've got the same situation on our mainframes.) > Keith: you want to use DataSources to define the location > of the DB via JNDI, but earlier you said you wanted to > supply authentication credentials on a per user basis. Those are not incompatible requirements. The DataSource interface includes a getConnection() method that takes a userid and password as arguments. > When you say 'per user' do you mean 'per client of my business', > or do you mean actual individual end-users of the application, > (the former I presume)? I think the latter; as mentioned above, most mainframe DBs do their own authentication and authorization checks. > I'm also not clear on why you're dead set against using connection > pooling, would you mind explaining? He actually said he might try pooling later, but if so, he'll need a pool per client userid, not a global one. (Been there, done that.) - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
