[
https://issues.apache.org/jira/browse/TAP5-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225246#comment-13225246
]
Denis Stepanov commented on TAP5-1842:
--------------------------------------
If you don't want "two ways" there is no need for the @Startup in the first
place, your argument doesn't make much sense to me, I'm sorry. I thought that
Tapestry motto is "code less", so if there is a second way with less code, why
it's a bad thing?
Steve suggested on the mailing list the same improvement, why it doesn't count?
Denis
> @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
