[
https://issues.apache.org/jira/browse/ISIS-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720256#comment-14720256
]
ASF subversion and git services commented on ISIS-1044:
-------------------------------------------------------
Commit 4ac11bbcae21f3279cb8de13b0276c6961613ce2 in isis's branch
refs/heads/ISIS-1044 from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=4ac11bb ]
ISIS-1044: introducing interaction contexts - analogous to those
visibility/usability/validity checking, for accessing properties, collections,
invoking actions; also action prompt (for choices and autoComplete).
This commit rationalizes the metamodel API to use contexts in a more consistent
manner for the accessors as well as the business rule checks. The idea is for
the caller to provide a context, but to leave the AuthenticationSession as null
if no visibility filtering is to be performed.
Have not, as of yet, removed the InteractionUtils#withFiltering, nor the
AuthenticationSession and DeploymentCategory from the various method calls
(these will be removed in a later commit).
> Table counts and gmap3/fullcalendar2 do not honour any vetoing, eg by
> subscribers or WithApplicationTenancy
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISIS-1044
> URL: https://issues.apache.org/jira/browse/ISIS-1044
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: viewer-wicket-1.7.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.10.0
>
>
> Suppose that the Isis addon security module is being used with application
> tenancy checking; this means that the Wicket table
> (CollectionContentsAsAjaxTable) will only show rows for those entities for
> which the user is authorized (the visibility has not been vetoed).
> However, the underlying EntityCollectionModel does contain those objects, and
> the size of that collection is what is shown in the "showing 1-5 of 15"
> totals etc rendered at the bottom of the table.
> So the question is: how to ensure that figure is correct?
> * One option is to eagerly check the visibility of every item (even those not
> on the current page).
> * Another option is to suppress the totals, somehow (would require additional
> metadata, along with a worse UI for users
> ~~~
> Related: the gmap3/fullcalendar2/excel Isis addons do not check for the
> object visibility, meaning that they expose information when they should not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
