hello, i've got a question regarding the best way to handle db connection pooling. we are using jrun 3.0 which provides jrun specific jdbc connection pooling, but i prefer to use jdbc 2.0 connection pooling (our driver supports it) for maximum portability between app servers. i have read many of the discussions in the archive regarding holding a connection pool in the servlet context. this method would work fine for us if we were only doing web based apps. however, i would like to provide a vendor neutral way for ejbs, or any other type of java app to get a database connection. i have been playing around with the idea of having a stateless session bean that maintains a db connection pool that would then hand out connections to requesting services. i'm not sure if this would work but am working on implementing it. has anyone tried this, or are there better mechanisms for providing app server vendor neutral jdbc connection pools to ejbs, servlets, and other clients? thanks for the input, chris =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". Some relevant FAQs on JSP/Servlets can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
