Details

Description

Introduce data beans for configuration of the DefaultRunnableManager. This will give the chance to add customized configurations without the need of patch the configuration deployed with the jar file.
The new way of configuration uses a bean-map to get the configurations -> Every bean implementing the interface ''org.apache.cocoon.components.thread.ThreadPoolConfiguration" will be taken as single thread-pool configuration. The two (already existing) configurations "default, daemon" will still be deployed with the jar.

> > Giacomo Pati schrieb:
>> >> 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.
> >

Felix Knecht
added a comment - 06/Mar/07 18:42 After some discussions I think also, that Giacomos suggestion is a good
way to go. So I will change
https://issues.apache.org/jira/browse/COCOON-2019 to go in this direction.
<snip />
> > Giacomo Pati schrieb:
>> >> 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.
> >

Refactored ThreadPool. Break out the ThreadPool into a bean. This will
make it easier to configure custom thread pools for the RunnableManager.
The RunnableManager will load all thread pools implementing the interface
'ThreadPool'.

A new thread pool can be added by defining the custom thread pool to add
in your spring configuration: