Hello! I've just stumbled again at https://issues.apache.org/jira/browse/TAP5-1305, which boiled down to Tapestry-IoC dropping a contribution to an ordered configuration if there's another contribution with the same id. I fixed it specifically for service decorators. For service configurations, it remained the same: the contribution is dropped with a warning in the log, but I think this is easy to overlook and can cause errors which are difficult to spot since you consider that all contributions.
What do you think of making contributing two different values to an ordered configuration with the same id a show-stopping error? -- Thiago
