You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/11/03 16:14:50 UTC

[jira] Created: (TAPESTRY-1881) Add support for startup() methods in modules, as an easy way to add startup logic

Add support for startup() methods in modules, as an easy way to add startup logic
---------------------------------------------------------------------------------

                 Key: TAPESTRY-1881
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1881
             Project: Tapestry
          Issue Type: Improvement
          Components: tapestry-ioc
    Affects Versions: 5.0.6
            Reporter: Howard M. Lewis Ship
            Priority: Minor


There's a mechanism for adding startup logic, by contributing to the RegistryStartup service configuration.

It would be nice if there was an optimized way to accomplish the same thing, i.e., starutp() methods (with injected parameters) as an easier way to accomplish the same thing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-1881) Add support for startup() methods in modules, as an easy way to add startup logic

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-1881:
-------------------------------------------

    Fix Version/s: 5.1

> Add support for startup() methods in modules, as an easy way to add startup logic
> ---------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1881
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1881
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.0.6
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.1
>
>
> There's a mechanism for adding startup logic, by contributing to the RegistryStartup service configuration.
> It would be nice if there was an optimized way to accomplish the same thing, i.e., starutp() methods (with injected parameters) as an easier way to accomplish the same thing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAP5-104) Add support for startup() methods in modules, as an easy way to add startup logic

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-104:
--------------------------------------

    Issue Type: New Feature  (was: Bug)

> Add support for startup() methods in modules, as an easy way to add startup logic
> ---------------------------------------------------------------------------------
>
>                 Key: TAP5-104
>                 URL: https://issues.apache.org/jira/browse/TAP5-104
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> There's a mechanism for adding startup logic, by contributing to the RegistryStartup service configuration.
> It would be nice if there was an optimized way to accomplish the same thing, i.e., starutp() methods (with injected parameters) as an easier way to accomplish the same thing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org