excuse me that 'ori8' not ora8

  > -----Original Message-----
  > From: malcolm davis [mailto:[EMAIL PROTECTED]]
  > Sent: Wednesday, March 28, 2001 10:16 PM
  > To: [EMAIL PROTECTED]
  > Subject: RE: Pooling with Oracle database
  > 
  > 
  > Rafal,
  > 
  > You might want to change from the thin to ora8.
  > 'ora8' was designed to be used for connection pooling.
  > The 'thin' driver was developed for applets.
  > 
  > - malcolm
  > 
  >   > -----Original Message-----
  >   > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
  >   > Sent: Wednesday, March 28, 2001 7:41 PM
  >   > To: [EMAIL PROTECTED]
  >   > Subject: Re: Pooling with Oracle database
  >   > 
  >   > 
  >   > 
  >   > 
  >   > On Wed, 28 Mar 2001, Rafal Zakrzewski wrote:
  >   > 
  >   > > Hello,
  >   > > 
  >   > > How to encode one pool of connections for whole application ?
  >   > > Should I encode this in some main servlet and then 
  > receive connection
  >   > > from this servlet ?
  >   > > 
  >   > > In struts-config.xml I have a section:
  >   > >     <data-sources>
  >   > >     <data-source autoCommit="false"
  >   > >        description="Trial access to database"
  >   > >         driverClass="oracle.jdbc.driver.OracleDriver"
  >   > >         maxCount="4"
  >   > >         minCount="2"
  >   > >         password="123"
  >   > >              url="jdbc:oracle:thin:@ado:1521:123"
  >   > >              user="123" />
  >   > > 
  >   > >   </data-sources>
  >   > > 
  >   > > 
  >   > > tnx
  >   > > 
  >   > 
  >   > With this entry in struts-config.xml, Struts will create a single
  >   > connection pool, and will also make it available in different ways:
  >   > 
  >   > * If you have a reference to the controller servlet (as in 
  > an Action),
  >   >   you can call servlet.findDataSource(null);
  >   > 
  >   > * If you have access to the servlet context (as in a 
  > different servlet
  >   >   in the same webapp), you can call
  >   >   getServletContext().getAttribute(Action.DATA_SOURCE_KEY);
  >   > 
  >   > * In a custom tag implementation class, you can call
  >   >   pageContext.getAttribute(Action.DATA_SOURCE_KEY,
  >   >    PageContext.APPLICATION_SCOPE);
  >   > 
  >   > * In a scriptlet embedded in a JSP page, you can call
  >   >   application.getAttribute(Action.DATA_SOURCE_KEY);
  >   > 
  >   > In all of these cases you are referencing exactly the same 
  > connection
  >   > pool.
  >   > 
  >   > Craig
  >   > 

Reply via email to