tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago H. de Paula Figueiredo (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1842) @Startup should support id and constraints
Date Tue, 06 Mar 2012 13:50:57 GMT

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

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

On Tue, 06 Mar 2012 10:32:58 -0300, Dragan Sahpaski (Commented) (JIRA)  

Doesn't contributing to the RegistryStartup service, which has an ordered  
configuration, does exactly what's been asked here? I don't see the need  
for two different ways to do the same thing. As far as I can see, @Startup  
was meant to be used in simpler cases (without ordering).

Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,  
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.

> @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


View raw message