[
https://issues.apache.org/jira/browse/TAP5-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223260#comment-13223260
]
Igor Drobiazko commented on TAP5-1842:
--------------------------------------
If I remember correctly, we had this discussion already. IMO, @Startup
shouldn't have any order. If you need some kind of order, do it as Thiago
suggested or build your own service with ordered configuration which you
inject into a startup method.
On Tue, Mar 6, 2012 at 2:48 PM, Thiago H. de Paula Figueiredo <
--
Best regards,
Igor Drobiazko
http://tapestry5.de
http://twitter.com/drobiazko
> @Startup should support id and constraints
> ------------------------------------------
>
> Key: TAP5-1842
> URL: https://issues.apache.org/jira/browse/TAP5-1842
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Reporter: Denis Stepanov
>
> It would be nice to have something like:
> @Startup(id = "DBInit", constraints = "before:*")
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
