What you want does not scale. You need to pool DB connections. This contradicts a per-user authentication with the DB. You can however write a JAAS login module that authenticates against the users of a DB. But in the backend you must use one single (technical) DB user for your application (DS) that performs all the work.
DB user management as detailed as in products like Oracle is historic (client-server era) and if of no real use for distributed applications today. I mean those DBs even have stuff like stored procedures that enable you to actually write whole applications inside the DB (Oracle Portal as an example). Just because a feature exists that is not a reason to use it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907226#3907226 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3907226 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
