[
https://issues.apache.org/jira/browse/ISIS-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541582#comment-17541582
]
ASF subversion and git services commented on ISIS-3063:
-------------------------------------------------------
Commit 425eb37810d17f81a4787349d5dc2807ea5f9000 in isis's branch
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=425eb37810 ]
ISIS-3063: just cleaning up prev. commit
> [Programming Model] Support for (Logical Type Name) Aliases
> -----------------------------------------------------------
>
> Key: ISIS-3063
> URL: https://issues.apache.org/jira/browse/ISIS-3063
> Project: Isis
> Issue Type: New Feature
> Components: Isis Applib (programming model)
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-RC1
>
>
> h2. Goals:
> * Support bookmark resolution to handle alias names. (Introduce `@Aliased`
> annotation)
> * Support for `@Named` annotation on concrete types, abstract types and
> interfaces.
> * Deprecate annotation `@LogicalTypeName`.
> * Deprecate annotation attribute `@DomainObject(logicalTypeName=...)`.
> h2. Non Goals:
> * No injection point resolution based on alias names. (Naturally so, because
> it is based on types not names anyway.)
> * No modification to the Security Model (SecMan): Permissions are checked
> against primary logical member names, not involving aliases.
> h2. Implications:
> * Must be supported by SpecificationLoader#specForBookmark and Restful
> DomainObjectResource and its friends.
> * Must also support service lookup based on alias names (ServiceRegistry).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
