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)" <ta...@jakarta.apache.org> on 2007/03/08 21:01:27 UTC
[jira] Created: (TAPESTRY-1330) It should be possible to place the
@Lifecycle annotation on the service interface, as well as on the builder
method
It should be possible to place the @Lifecycle annotation on the service interface, as well as on the builder method
-------------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-1330
URL: https://issues.apache.org/jira/browse/TAPESTRY-1330
Project: Tapestry
Issue Type: New Feature
Components: tapestry-ioc
Affects Versions: 5.0
Reporter: Howard M. Lewis Ship
In many cases, the design of a particular service interface is inextricably linked to the service lifecycle, such as @Lifecycle("perthread"). Being able to place this annotation on the service interface is of benefit because it is self documenting, and because it ensures that the service uses the lifecycle, if the developer forgets to place the annotation on the service builder method. @Lifecycle should be allowed on classes as well as methods to support this.
--
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] Closed: (TAPESTRY-1330) The @Scope annotaton should be
allowed on service implementation classes (in addition to service builder
methods inside a module class)
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1330.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.4
> The @Scope annotaton should be allowed on service implementation classes (in addition to service builder methods inside a module class)
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1330
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1330
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
> Fix For: 5.0.4
>
>
> In many cases, the design of a particular service interface is inextricably linked to the service lifecycle, such as @Lifecycle("perthread"). Being able to place this annotation on the service interface is of benefit because it is self documenting, and because it ensures that the service uses the lifecycle, if the developer forgets to place the annotation on the service builder method. @Lifecycle should be allowed on classes as well as methods to support this.
--
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] Commented: (TAPESTRY-1330) It should be possible to place
the @Lifecycle annotation on the service interface, as well as on the
builder method
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489269 ]
Howard M. Lewis Ship commented on TAPESTRY-1330:
------------------------------------------------
A variation of this is checked in; autobuilding a service allows the @Scope annotation (the renamed version of @Lifecycle) to be placed on the service implementation class.
> It should be possible to place the @Lifecycle annotation on the service interface, as well as on the builder method
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1330
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1330
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
>
> In many cases, the design of a particular service interface is inextricably linked to the service lifecycle, such as @Lifecycle("perthread"). Being able to place this annotation on the service interface is of benefit because it is self documenting, and because it ensures that the service uses the lifecycle, if the developer forgets to place the annotation on the service builder method. @Lifecycle should be allowed on classes as well as methods to support this.
--
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-1330) The @Scope annotaton should be
allowed on service implementation classes (in addition to service builder
methods inside a module class)
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1330:
-------------------------------------------
Summary: The @Scope annotaton should be allowed on service implementation classes (in addition to service builder methods inside a module class) (was: It should be possible to place the @Lifecycle annotation on the service interface, as well as on the builder method)
> The @Scope annotaton should be allowed on service implementation classes (in addition to service builder methods inside a module class)
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1330
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1330
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
> Fix For: 5.0.4
>
>
> In many cases, the design of a particular service interface is inextricably linked to the service lifecycle, such as @Lifecycle("perthread"). Being able to place this annotation on the service interface is of benefit because it is self documenting, and because it ensures that the service uses the lifecycle, if the developer forgets to place the annotation on the service builder method. @Lifecycle should be allowed on classes as well as methods to support this.
--
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] Assigned: (TAPESTRY-1330) It should be possible to place the
@Lifecycle annotation on the service interface, as well as on the builder
method
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-1330:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> It should be possible to place the @Lifecycle annotation on the service interface, as well as on the builder method
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1330
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1330
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
> Fix For: 5.0.4
>
>
> In many cases, the design of a particular service interface is inextricably linked to the service lifecycle, such as @Lifecycle("perthread"). Being able to place this annotation on the service interface is of benefit because it is self documenting, and because it ensures that the service uses the lifecycle, if the developer forgets to place the annotation on the service builder method. @Lifecycle should be allowed on classes as well as methods to support this.
--
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