You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/03/05 15:36:38 UTC

[jira] [Commented] (TAP5-1566) Extend OrderedConfguration with new methods to fine-tune ordering

    [ https://issues.apache.org/jira/browse/TAP5-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348796#comment-14348796 ] 

Jochen Kemnade commented on TAP5-1566:
--------------------------------------

I wonder if this is still relevant. What kind of API did you have in mind?

> Extend OrderedConfguration with new methods to fine-tune ordering
> -----------------------------------------------------------------
>
>                 Key: TAP5-1566
>                 URL: https://issues.apache.org/jira/browse/TAP5-1566
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>
> When mixing and matching different libraries that make contributions to the same configuration (often a pipeline), it would be nice if there was an API on OrderedConfiguration to provide additional ordering constraints. For example, two different contributions to ComponentRequestHandler may want to be in the first slot, and the application developer may need to correct this to ensure a correct and consistent ordering.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)