[
https://issues.apache.org/jira/browse/TAP5-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225726#comment-13225726
]
Josh Canfield commented on TAP5-1842:
-------------------------------------
There is a vote button in the defect. If you care about the feature vote it up.
Comments are nice but number of comments doesn't bring the issue to the top of
the most wanted list.
I can't say that I've ever had a need for ordered @Startup methods, but I like
the idea of being able to create specific methods for specific tasks.
Having multiple @Startup methods seems pretty natural, and being able to define
their order would be nice.
I assume you're not asking to have this work across multiple modules? I often
break up a project into multiple modules and have my AppModule include them.
@Startup("before:method")
ModuleA.method1
ModuleB.method
@Startup("after:method")
ModuleA.method2
> @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
