You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Thiago Henrique De Paula Figueiredo (Jira)" <ji...@apache.org> on 2020/11/26 21:21:00 UTC
[jira] [Created] (TAP5-2649) Configuration and MappedConfiguration
should have consistent ordering
Thiago Henrique De Paula Figueiredo created TAP5-2649:
---------------------------------------------------------
Summary: Configuration and MappedConfiguration should have consistent ordering
Key: TAP5-2649
URL: https://issues.apache.org/jira/browse/TAP5-2649
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-ioc
Affects Versions: 5.3, 5.4
Reporter: Thiago Henrique De Paula Figueiredo
Assignee: Thiago Henrique De Paula Figueiredo
Fix For: 5.4
Depending on the order in which module classes with contributions to the same service with OrderedConfiguration were added to the Registry, which isn't defined, the resulting list passed to the service can have different ordering. Given the same contributions, the resulting list should always be the same.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)