You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/09/17 09:43:53 UTC
[jira] [Commented] (ISIS-473) Allow operations to individually be
specified for "@bookmarkable" behaviour.
[ https://issues.apache.org/jira/browse/ISIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769294#comment-13769294 ]
ASF subversion and git services commented on ISIS-473:
------------------------------------------------------
Commit 9197e40c980d06287107a06f3d3acd2c8f3b64ee in branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=9197e40 ]
ISIS-473: actions now need to be explicitly annotated as @Bookmarkable
(they must also have safe semantics, as previously).
> Allow operations to individually be specified for "@bookmarkable" behaviour.
> ----------------------------------------------------------------------------
>
> Key: ISIS-473
> URL: https://issues.apache.org/jira/browse/ISIS-473
> Project: Isis
> Issue Type: Improvement
> Components: Core, Viewer: Wicket
> Affects Versions: viewer-wicket-1.2.0
> Reporter: David Tildesley
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: viewer-wicket-1.3.0
>
>
> The bookmarks tab gets filled up quickly with operations from an object that is marked as @bookmarkable. It would be better to have finer grained control over which operations (if any) are bookmarked. Maybe it is easier to overide the existing behaviour by a @bookmarkable parameter for an operation that effectively prevents the operation from becoming bookmarked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira