[JAMES-495] Decide how to replace Avalon Configuration

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0-M1
• Component/s: James Core
• Assignee: Norman Maurer
• Reporter: Stefano Bagnara
• Created: 15/May/06 00:02
• Updated: 12/Jan/10 22:07
• Resolved: 12/Jan/10 22:07

Description

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?

Issue Links

• incorporates: JAMES-415 Support dynamic reload of servernames