You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by "Niclas Hedhman (JIRA)" <ji...@apache.org> on 2017/04/10 05:51:41 UTC
[jira] [Commented] (POLYGENE-133) Document & Test @Concerns and
@SideEffects on methods.
[ https://issues.apache.org/jira/browse/POLYGENE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962463#comment-15962463 ]
Niclas Hedhman commented on POLYGENE-133:
-----------------------------------------
This was actually not implemented. But I have added this feature and tried to document both this and the feature of having @Concerns/@SideEffects on custom annotations.
However, more documentation is needed in this field, as it is an important aspect (pun intended), or should we say "concern" (pun 2), of Polygene itself.
> Document & Test @Concerns and @SideEffects on methods.
> ------------------------------------------------------
>
> Key: POLYGENE-133
> URL: https://issues.apache.org/jira/browse/POLYGENE-133
> Project: Polygene
> Issue Type: Task
> Affects Versions: 2.0, 2.1
> Reporter: Niclas Hedhman
> Assignee: Niclas Hedhman
> Fix For: 3.0
>
>
> There is code that seems to indicate that it is possible to declare @Concerns and @SideEffects directly on the methods, instead of the whole composite/mixin (with subsequent AppliesToFilters if InvocationHandler).
> We need to document and test this feature.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)