This works for apache dbcp ... I hope it's similar for proxool 

<service-point id="IdDatasource" interface="javax.sql.DataSource">
 <invoke-factory>
 <construct class="org.apache.commons.dbcp.BasicDataSource">
  <set property="driverClassName" value="oracle.jdbc.driver.OracleDriver" />

  <set property="url" value="${db.url}" /> 
  <set property="username" value="${db.user}" /> 
  <set property="password" value="${db.password}" /> 
  </construct>
  </invoke-factory>
  </service-point>
  _____________________________________________________________________
Default Config für Testumgebung 
 <contribution configuration-id="hivemind.FactoryDefaults">
  <default symbol="db.url" value="jdbc:oracle:thin:@server:1521:sid" /> 
  <default symbol="db.user" value="user" /> 
  <default symbol="db.password" value="pass" /> 
  </contribution>

> -----Original Message-----
> From: Rui Pacheco [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 16, 2006 3:54 PM
> To: Tapestry users
> Subject: Re: ServletContext
> 
> 
> I dont doubt HiveMind would be the right way to go, but the 
> learning curve
> seems to be a bit too steep for my timeframe.
> Can I insist on an example using ServletContextListener, ie, 
> something that
> being all in Java would be more in my reach?
> 
> On the other hand, if someone has configured a connection pool (any or
> Proxool in particular) using HiveMind and is willing to share 
> the example, I
> would be more than gratefull.
> 
> 
> On 5/16/06, Hugo Palma <[EMAIL PROTECTED]> wrote:
> >
> > In that case, why don't you configure Proxool as a service in you
> > hivemodule.xml file ? That's where your service 
> configuration should take
> > place.
> >
> > My ServletContextListener suggestion usually works well 
> when you have a
> > properties bundle that you want to place outside the war so 
> that it can be
> > easily changed. In your case i think the most appropriate is to use
> > hivemind
> > configurations to do the job.
> > Am i making sense here ?
> >
> > On 5/16/06, Rui Pacheco <[EMAIL PROTECTED]> wrote:
> > >
> > > Ok...
> > > The properties file holds configuration data for Proxool, 
> the connection
> > > pool I'm using with my application.
> > >
> > > On 5/16/06, James Carman <[EMAIL PROTECTED]> wrote:
> > > >
> > > > First of all, what does that properties file contain?  You know,
> > > HiveMind
> > > > is
> > > > a configuration microkernel, so you can do a lot of 
> configuration with
> > > > HiveMind.
> > > >
> > > > -----Original Message-----
> > > > From: Rui Pacheco [mailto:[EMAIL PROTECTED]
> > > > Sent: Tuesday, May 16, 2006 9:02 AM
> > > > To: Tapestry users
> > > > Subject: Re: ServletContext
> > > >
> > > > Could you or someone else give me an example on how to do that?
> > > >
> > > > On 5/16/06, Hugo Palma <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > I would implement such a feature using a 
> ServletContextListener.
> > > > Something
> > > > > like the HiveUtils SystemPropertyInitListener class.
> > > > >
> > > > > Cheers
> > > > >
> > > > > Hugo
> > > > >
> > > > > On 5/16/06, Rui Pacheco <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > Hi all
> > > > > >
> > > > > > I was planning on storing a properties file inside 
> my WEB-INF
> > > > directory
> > > > > > and
> > > > > > then read it using getResourceAsStream from 
> ServletContext, but
> > > > > apparently
> > > > > > I
> > > > > > can't access the ServletContext from inside Tapestry.
> > > > > > Is there another way to read the properties file or 
> how to get to
> > my
> > > > > > ServletContext?
> > > > > >
> > > > > > --
> > > > > > Cumprimentos,
> > > > > > Rui Pacheco
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Cumprimentos,
> > > > Rui Pacheco
> > > >
> > > >
> > > >
> > > > 
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > > --
> > > Cumprimentos,
> > > Rui Pacheco
> > >
> > >
> >
> >
> 
> 
> -- 
> Cumprimentos,
> Rui Pacheco
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to