[
https://issues.apache.org/jira/browse/TAP5-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348781#comment-14348781
]
Jochen Kemnade commented on TAP5-1719:
--------------------------------------
We could still address this for 5.4. I also get the urge to override parts of
the {{TypeCoercer}} configuration from time to time.
> Deprecate Configuration type, and replace with OrderedConfiguration
> -------------------------------------------------------------------
>
> Key: TAP5-1719
> URL: https://issues.apache.org/jira/browse/TAP5-1719
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core, tapestry-ioc
> Affects Versions: 5.3, 5.4
> Reporter: Howard M. Lewis Ship
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
