On Mon, Jun 24, 2002 at 04:44:47PM +0000, Corey Jewett wrote: > Great. I poked down through the ECM code and it makes sense what's going > on now. Is the configuration just part of my regular xconf? i.e. > > <guardian pool-min="5" pool-max="25"/>
Yes. > More importantly I'm curious as to why excalibur.datasource internalizes > the pooling rather than utilize PoolableComponentHandler. Is it simply > so there is no dependancy there? By internalize, do you mean via the pool-controller tag, instead of like your example above ? Good question, I had to think about it :-) Remember, PoolableComponentHandler is for top level components accessed by ECM.lookup()/ECS.select(), etc. We don't actually want the DataSource component to be pooled, we want the underlying Connection objects it manages to be pooled. This is why DataSourceComponent implements ThreadSafe (so we get the same instance each lookup()/select()), and why it uses an underlying pool for Connection objects that it returns via getConnection(). Hope that helps. Cheers, Marcus -- ..... ,,$$$$$$$$$, Marcus Crafter ;$' '$$$$: Computer Systems Engineer $: $$$$: ManageSoft GmbH $ o_)$$$: 82-84 Mainzer Landstrasse ;$, _/\ &&:' 60327 Frankfurt Germany ' /( &&& \_&&&&' &&&&. &&&&&&&: -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>