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 "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/01/12 23:07:55 UTC
[jira] Resolved: (JAMES-495) Decide how to replace Avalon
Configuration
[ https://issues.apache.org/jira/browse/JAMES-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved JAMES-495.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: Trunk)
3.0-M1
Assignee: Norman Maurer
We replaced it with Commons-Configuration in trunk..
> Decide how to replace Avalon Configuration
> ------------------------------------------
>
> Key: JAMES-495
> URL: https://issues.apache.org/jira/browse/JAMES-495
> Project: JAMES Server
> Issue Type: Sub-task
> Components: James Core
> Affects Versions: 3.0
> Reporter: Stefano Bagnara
> Assignee: Norman Maurer
> Fix For: 3.0-M1
>
>
> We could switch to Commons-configuration or Obix configuration framework, or anything else.
> How should we configure our object?
> Using configuration beans like we did in SMTPHandlerConfiguration?
> Imho we should use something that allow us to:
> 1) hot-reload configurations or part of configurations
> 2) store configuration in JNDI
> 3) simplify manageability of configuration from JMX
> Any comment/proposal on that?
> It would be easy to refactor our components to use "commons Configuration" object instead of "avalon Configuration" (A wrapper between the 2 configurations already exists): does it help?
--
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