Re: JNDI DataSource - need to synchronize?

[Marco Tedone <mt...@jemos.org>]

Well, to be sure, put your variables inside the methods. This way, your data
will be safe. One idea would be to create objects when you need them, and to
close them when you've finished.

Marco
----- Original Message ----- 
From: "john-paul delaney" <jp...@justatest.com>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Sunday, September 07, 2003 12:18 PM
Subject: JNDI DataSource - need to synchronize?


> Hello List...
>
> Some coding help please.  Following earlier advice on this list and the TC
datasource how-to, I've now got a working test servlet.  Basically I declare
the Context(s) and DataSource as instance variables, and initialize them in
init:
>
> ========================================================
>    Context initContext = null;
>    Context envContext = null;
>    DataSource ds = null;
>
>    public void init() throws ServletException {
>
>       try {
>       initContext = new InitialContext();
>
>       envContext = (Context) initContext.lookup(
>          "java:comp/env");
>       ds = (DataSource) envContext.lookup(
>          "jdbc/jpdb");
>       } catch (NamingException e) {
>
>          throw new ServletException(
>             "Couldn't setup JNDI Context/DataSource", e);
>
>       }
>    }
> ==========================================================
>
> If this is the correct approach, should I be synchronizing the
Context(s)/DataSource in the doGet method?  If another http request thread
closes it's own connection, will it affect the Context or DataSource object
of this request?
>
> Thanks for any clarification,
> /j-p.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>