[
https://issues.apache.org/jira/browse/TAP5-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223286#comment-13223286
]
Denis Stepanov commented on TAP5-1842:
--------------------------------------
Yes it does, but it is a lot messier, you need an inner class, and so on.
Specialy when you are using @Startup and then you need an order.
Whole purpose of the @Startup is that you don't need to add an contribution, as
it says in JavaDoc:
"Instead of making contributions to the RegistryStartup service configuration
you can provide startup methods inside your modules."
There are many cases in Tapestry when you can do one thing in two different
ways, it doesn't mean it's a bad thing.
It doesn't have an order when you don't need it, if you want an order you can
have it. I don't see why anyone should be against it.
If there is already @Startup annotation why not to make it more useful?
Denis
Mar 6, 2012 v 2:54 PM, Igor 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
