You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (Created) (JIRA)" <ji...@apache.org> on 2011/10/24 17:51:32 UTC

[jira] [Created] (TAP5-1719) Deprecate Configuration type, and replace with OrderedConfiguration

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
            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira