[jira] [Closed] (TAP5-782) Tapestry should demarcate, via documentation annotations, user-access-only vs. user-implementable interfaces

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade closed TAP5-782.
-------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen the issue and adjust the "Affected Version/s" property.

> Tapestry should demarcate, via documentation annotations, user-access-only vs. user-implementable interfaces
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-782
>                 URL: https://issues.apache.org/jira/browse/TAP5-782
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.1.0.5
>            Reporter: Robert Zeigler
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> It would be nice if there was a documenting annotation on interfaces to inform users which interfaces can be used by user-code but never implemented, verses those interfaces which may be implemented at some point by users.  Examples of the former include most of the interfaces in the org.apache.tapestry5.model package.  The Asset and Resource interfaces are examples of the second class.



--
This message was sent by Atlassian JIRA
(v6.2#6252)