Just committed this. Please see the PoolableComponentHandler javadocs for details.
Leif Mortenson wrote: > Berin posted a vote the other day to use the ResourceLimitingPool for > this. If that change is made, then you would be able to get both sets > of funtionality simply by adding a pool-strict attribute. Blocking > support could also be added with pool-blocking and pool-block-timeout > attributes. > > Leif > > Mark Woon wrote: > >> Leif Mortenson wrote: >> >> >>> If your component implements Poolable, this is as simple as adding the >>> following attributes to your component definition: >>> >>> <mycomponent pool-min="1" pool-max="10" pool-grow="1"> >>> <dbpool>my-db</dbpool> >>> </mycomponent> >>> >> >> Is there a way to specify what kind of Pool the CM should use (eg. >> HardResourceLimitingPool vs. SoftResourceLimitingPool)? >> >> Thanks, >> -Mark >> >> >> -- >> To unsubscribe, e-mail: >> <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: >> <mailto:[EMAIL PROTECTED]> >> >> >> > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
