[jira] [Commented] (TAP5-1565) It should be easier to make a series of contributions to an OrderedConfiguration so that the contributions are in sequential orderer

["Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>]

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

Thiago H. de Paula Figueiredo commented on TAP5-1565:
-----------------------------------------------------

Related to TAP5-2358.

> It should be easier to make a series of contributions to an OrderedConfiguration so that the contributions are in sequential orderer
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1565
>                 URL: https://issues.apache.org/jira/browse/TAP5-1565
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3
>
>
> It is not uncommon to have a series of elements to add to an OrderedConfiguration in a specific order; it would be nice if there was a way to add sequential items without manually tracking each nodes name and adding "after:" clauses.
> Example:
>   configuration.add("item1", new Item1());
>   configuration.addSequential("item2", new Item2());
>   configuration.addInstanceSequential("item3", Item3.class);
> This would simply add an "after:item1" ordering constraint for item2, and an "after:item3" constraint for item3.
> It should be legal to add an item sequentially, even if there is no previously added item (added in this contribution method, or elsewhere), in which case, no ordering constraint it added.
> Would "next" and "nextInstance" be better than "addSequential" and "addInstanceSequential"?  I'm open to other suggestions on the naming.



--
This message was sent by Atlassian JIRA
(v6.2#6252)