Cezar wrote:
>Not counting an ideal JDBC driver with "su" capabilities.. bet if
there are
>two JDBC drivers with such behaviour they implement it using
different
>proprietary calls().
Cezar is quite right. The sensible way to do this is to create an
invidual java.sql.Connection for each user as and when they log in and
keep it in a session.
You could wrap the Connection is some sort of AuthenticationProvider
if you're really worried about security.
A simple package for doing this is available as part of Paperclips
(an open source servlet server).
You can get Paperclips from
http://www.tapsellferrier.co.uk/engine.html
Nic Ferrier
Tapsell-Ferrier Ltd
www.tapsellferrier.co.uk
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
