There is one other possibility I neglected to mention.... Option 3.14) (I pick 3.14 as it's related to option 3.) You could use the Java Connector Architecture (JCA) to create your own connector DataSource. The application server would then manage the complexities of connection pooling along with authentication and security. In your connector then, you'd simply take the users identity given by the app server and use it to log into the database. The option assumes that both your JDBC driver and your app server support the JCA. It also assumes you're comfortable with all the complexities of writing a connector.
This option is a rather interesting one, and I don't think it's been tried before and would make for an interesting project which I think could be fun. However, in reality you should go with the simplest solution meeting your needs. Most likely this means either: 1) Using BMP to do bean-managed authentication with the database, or 2) Merging everything into 1 database and manage security at the application level. Doug Consultant and Enterprise Architect =========================================================================== 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".
