[
https://issues.apache.org/jira/browse/TAP5-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thiago H. de Paula Figueiredo updated TAP5-2358:
Description: 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. (was: Depending on the order in which module
classes with contributions to the same service with OrderedConfiguration, the
resulting list passed to the service can have different ordering. Given the
same contributions, the resulting list should always be the same.)
> OrderedConfiguration should have consistent ordering
>
>
> Key: TAP5-2358
> URL: https://issues.apache.org/jira/browse/TAP5-2358
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
>Affects Versions: 5.3, 5.4
>Reporter: Thiago H. de Paula Figueiredo
>Assignee: Thiago H. de Paula Figueiredo
> Labels: month-of-tapestry
>
> 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
(v6.2#6252)
