You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Andi Huber (Jira)" <ji...@apache.org> on 2021/12/13 07:53:00 UTC
[jira] [Resolved] (ISIS-2916) Introduce @LogicalTypeName to properly map abstract types onto the security model
[ https://issues.apache.org/jira/browse/ISIS-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andi Huber resolved ISIS-2916.
------------------------------
Resolution: Resolved
Experimental feature.
> Introduce @LogicalTypeName to properly map abstract types onto the security model
> ---------------------------------------------------------------------------------
>
> Key: ISIS-2916
> URL: https://issues.apache.org/jira/browse/ISIS-2916
> Project: Isis
> Issue Type: Improvement
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M7
>
>
> Take for example from the demo a type, which is implemented by JDO/JPA entity types and a viewmodel:
> public interface WrapperDoubleHolder { ... }
> We need a programming model such that we can declare for this interface, which logical-type it maps to, when deciding whether a logged on user has access to this type or not.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)