You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Felix Knecht (JIRA)" <ji...@apache.org> on 2007/03/05 22:50:51 UTC
[jira] Updated: (COCOON-2019) Make DefaultRunnableManager custom
configurable
[ https://issues.apache.org/jira/browse/COCOON-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Knecht updated COCOON-2019:
---------------------------------
Attachment: DefaultRunnableManager.diff
The patch
> 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.