[TAP5-1719] Deprecate Configuration type, and replace with OrderedConfiguration

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.3, 5.4
• Component/s: tapestry-core, tapestry-ioc
• Assignee: Unassigned
• Reporter: Howard Lewis Ship
• Created: 24/Oct/11 15:50
• Updated: 05/Mar/15 14:31

Description

Over time, the use of the unordered Configuration type has proven to be a problem, since contributions to such a configuration can't have an override.

It would be nice if Configuration were deprecated, leaving just two types of configuration: Ordered and Mapped.

Where Configuration is currently used, it could be wrapped as an OrderedConfiguration, with ids automatically generated in some way.