Thanx very much Craig!!! The reason I went thru this whole thing was that I
DIDNT wanted to have a JDBC Pooling kinda mechanism, I mean I am doing the
user authentication via backend(oracle db) login which means I would have to
create an explicit connection and maintain that for each user. First I was
going to put the DBManagerBean in session scope but I read in the
JSP-INTEREST mailing that stuffing connection in session is not a good
practice(serialization??) so I managed things like that via the loginbean.
Am I right on that??? So if I made my LoginBean of session scope and took
out the hashtable stuff(managing sessions) would that be a way around??
Nothing is an "application" scope as I see it including the DB connection
since its a per user/per session based thing.
Once Again Thnx!!!
Asim Imam
Application Developer
@AT&T Tax Systems Group
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
