Ok, but the question was why do you need _servlet_ context ?
We can follow the same way as JDBC : class.forName(...) etc.
>Storing the connection pool for an application in the attributes of a
>servlet context deals
>with these issues. The connection pool is available to all the servlets
>(and JSP pages) in
>your application -- and only to those classes. You can have more than >one
connection pool in
>the same app under different keys (if you need it), and you can install
>multiple apps, each
>in their own servlet context, with no risk of access by one app's classes >to
the other app's
>connection pool.
ColdJava: java server side programming
http://coldjava.hypermart.net
____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at
http://webmail.netscape.com.
___________________________________________________________________________
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
