You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org> on 2008/08/31 12:15:44 UTC

[jira] Created: (JSIEVE-29) Refactor ConfigurationManager

Refactor ConfigurationManager
-----------------------------

                 Key: JSIEVE-29
                 URL: https://issues.apache.org/jira/browse/JSIEVE-29
             Project: jSieve
          Issue Type: Sub-task
            Reporter: Robert Burrell Donkin


ConfigurationManager maintains maps of class names against logical names. The default settings are loaded from properties files. ConfigurationManager is a singleton.

Used by:
 * CommandManager
 * ComparatorManager
 * TestManager

If command manager, comparator and test manager separated into interface and implementation then this class would become responsible only for loading data for the default implementations. This could then be refactored to the Factory pattern.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] Assigned: (JSIEVE-29) Refactor ConfigurationManager

Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
     [ https://issues.apache.org/jira/browse/JSIEVE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Burrell Donkin reassigned JSIEVE-29:
-------------------------------------------

    Assignee: Robert Burrell Donkin

> Refactor ConfigurationManager
> -----------------------------
>
>                 Key: JSIEVE-29
>                 URL: https://issues.apache.org/jira/browse/JSIEVE-29
>             Project: JAMES jSieve
>          Issue Type: Sub-task
>            Reporter: Robert Burrell Donkin
>            Assignee: Robert Burrell Donkin
>             Fix For: 0.3
>
>
> ConfigurationManager maintains maps of class names against logical names. The default settings are loaded from properties files. ConfigurationManager is a singleton.
> Used by:
>  * CommandManager
>  * ComparatorManager
>  * TestManager
> If command manager, comparator and test manager separated into interface and implementation then this class would become responsible only for loading data for the default implementations. This could then be refactored to the Factory pattern.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] Closed: (JSIEVE-29) Refactor ConfigurationManager

Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
     [ https://issues.apache.org/jira/browse/JSIEVE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Burrell Donkin closed JSIEVE-29.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.3

ConfigurationManager is now a POJO. Configuration is parsed upon construction. 

> Refactor ConfigurationManager
> -----------------------------
>
>                 Key: JSIEVE-29
>                 URL: https://issues.apache.org/jira/browse/JSIEVE-29
>             Project: JAMES jSieve
>          Issue Type: Sub-task
>            Reporter: Robert Burrell Donkin
>             Fix For: 0.3
>
>
> ConfigurationManager maintains maps of class names against logical names. The default settings are loaded from properties files. ConfigurationManager is a singleton.
> Used by:
>  * CommandManager
>  * ComparatorManager
>  * TestManager
> If command manager, comparator and test manager separated into interface and implementation then this class would become responsible only for loading data for the default implementations. This could then be refactored to the Factory pattern.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org