cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Knecht <>
Subject Re: Configuration of RunnableManager
Date Tue, 06 Mar 2007 18:39:58 GMT
After some discussions I think also, that Giacomos suggestion is a good
way to go. So I will change to go in this direction.


> Giacomo Pati schrieb:
>> Hi Felix
>> Felix Knecht wrote:
>>> I wonder how to create/add my own configuration for the
>>> RunnableManager. At the moment, the given configuration is
>>> included in the deployed jar file (having configured 2 pools
>>> (default,daemon)). Changing this configuration seems not that
>>> easy as I need to 'patch' the existing configuration in the
>>> deployed jar file.
>>> Making configuration easier I'd prefer the the 'New Features for
>>> the spring configurator' and introduce a new bean just containing
>>> the configuration data for a pool which implementing a specific
>>> (helper) interface. Thus everybody can add his own threadpool
>>> configuration. The RunnableManager then will create thread pools
>>> for all found beans implementing this (helper) interface.
>> I'd suggest instead of only breaking out the configuration of a
>> thread pool, break out the hole thread pool itself into a bean.
>> This would reduce the complexity of the RunnableManager and would
>> make the ThreadPool beans have a little more responsability than
>> just holding config values.
>> WDYT?
> This would make things easier for blocks needing just a threadpool
> (like the cron block).
> On the otherhand its possible, that the RunnableManager must share a
> pool with anything else, because all Threadpool beans would be loaded
> into the runnable manager. This must be kept in mind when configuring
> the pool. Adding an optional flag to the threadpool bean indicating if
> the pool can should be used in the RunnableManager could solve this
> problem.
> Felix

View raw message