> Hi Remy, > > we also discussed the possibility of creating connection pools. In this case > we also found scenarios where it seems to make sense to have userid and > password in the store e.g. in the case you would like to allow dynamic > instanceation of connection pools. But however, this would also not confirm > to the original design you described below. What do you suggest how we can > come to a solution? Do you think it would be better to pass just the > CredentialsToken instead of passing the SlideToken to the store?
I understand why in some general cases you would need the credentials. In the general case, you shouldn't. For the connection pool scenario, it seems the current thinking is that it's a JNDI resource managed by the J2EE container (see the J2EE* stores). So Slide is not responsible for instatiating it at all. Usually, the connect method of a store will be called only once, during the initialization of the namespace. Also, I've been thinking about getting rid of the need to pass the tokens around altogether, by just associating them with the transaction context. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
