[jira] Commented: (COCOON-2019) Make DefaultRunnableManager custom configurable

["Felix Knecht (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COCOON-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478511 ] 

Felix Knecht commented on COCOON-2019:
--------------------------------------

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.
> > 


> Make DefaultRunnableManager custom configurable
> -----------------------------------------------
>
>                 Key: COCOON-2019
>                 URL: https://issues.apache.org/jira/browse/COCOON-2019
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: * Cocoon Core
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Felix Knecht
>             Fix For: 2.2-dev (Current SVN)
>
>         Attachments: DefaultRunnableManager.diff
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.