[
https://issues.apache.org/jira/browse/ISIS-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259339#comment-14259339
]
ASF subversion and git services commented on ISIS-985:
------------------------------------------------------
Commit 36821059753c813891f7c73c10a7249071bef365 in isis's branch
refs/heads/ISIS-985 from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=3682105 ]
ISIS-985: initial implementation... now filtering out objects from tables if
not visible.
Improvements still to do:
- try to avoid creating unnecessary lists
- move the filtering functionality out of CollectionContentsSortableDataProvider
- modify the EntityPage (or EntityPropertiesForm) to also use the
ObjectVisibilityEvent to determine if a 404 should be thrown.
> Filter collections so that objects that are not visible to the current user
> are not shown.
> ------------------------------------------------------------------------------------------
>
> Key: ISIS-985
> URL: https://issues.apache.org/jira/browse/ISIS-985
> Project: Isis
> Issue Type: New Feature
> Components: Core, Viewer: Wicket
> Affects Versions: viewer-wicket-1.7.0, core-1.7.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.8.0, core-1.8.0
>
>
> There are two bits to this.
> First, note that we have similar functionality when rendering an object
> itself, throwing a 404 if none of the object's members are visible. However,
> there should also be a check if the object itself is not visible, ie through
> a new ObjectVisibility check. (We already have ObjectValidity check as well
> as {Action/Property/Collection}Visibility, so all the required concepts exist.
> Second, the object visibility check should be used to determine if an object
> should be rendered in a collection/table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
