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/10/14 23:23:50 UTC
[jira] Created: (TAPESTRY-1829) Allow @Marker annotation on module
classes, to automatically mark all services of that module with the
annotation
Allow @Marker annotation on module classes, to automatically mark all services of that module with the annotation
-----------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-1829
URL: https://issues.apache.org/jira/browse/TAPESTRY-1829
Project: Tapestry
Issue Type: New Feature
Affects Versions: 5.0.5
Reporter: Howard M. Lewis Ship
This is very common for frameworks, if not for user (application) modules. You want to define a marker annotation, often as an inner class of the module, and mark all the services in that module with the annotation. That makes referencing a service in the module (for instance, so as to contribute to Alias) much simpler, and obviates the need to know the service id.
--
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-1829) Allow @Marker annotation on module
classes, to automatically mark all services of that module with the
annotation
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-1829:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> Allow @Marker annotation on module classes, to automatically mark all services of that module with the annotation
> -----------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1829
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1829
> Project: Tapestry
> Issue Type: New Feature
> Affects Versions: 5.0.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> This is very common for frameworks, if not for user (application) modules. You want to define a marker annotation, often as an inner class of the module, and mark all the services in that module with the annotation. That makes referencing a service in the module (for instance, so as to contribute to Alias) much simpler, and obviates the need to know the service id.
--
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-1829) Allow @Marker annotation on module
classes, to automatically mark all services of that module with the
annotation
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1829.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.7
> Allow @Marker annotation on module classes, to automatically mark all services of that module with the annotation
> -----------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1829
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1829
> Project: Tapestry
> Issue Type: New Feature
> Affects Versions: 5.0.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.7
>
>
> This is very common for frameworks, if not for user (application) modules. You want to define a marker annotation, often as an inner class of the module, and mark all the services in that module with the annotation. That makes referencing a service in the module (for instance, so as to contribute to Alias) much simpler, and obviates the need to know the service id.
--
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-1829) Allow @Marker annotation on
module classes, to automatically mark all services of that module with the
annotation
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534853 ]
Howard M. Lewis Ship commented on TAPESTRY-1829:
------------------------------------------------
The intent is that the provided default is used instead of null for all services that don't have a specific marker annotation.
> Allow @Marker annotation on module classes, to automatically mark all services of that module with the annotation
> -----------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1829
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1829
> Project: Tapestry
> Issue Type: New Feature
> Affects Versions: 5.0.5
> Reporter: Howard M. Lewis Ship
>
> This is very common for frameworks, if not for user (application) modules. You want to define a marker annotation, often as an inner class of the module, and mark all the services in that module with the annotation. That makes referencing a service in the module (for instance, so as to contribute to Alias) much simpler, and obviates the need to know the service id.
--
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