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/01/31 08:54:00 UTC
[jira] [Updated] (ISIS-2511) Rationalize all @Named("...")
@DomainXxx(objectType="...") namespaces.
[ https://issues.apache.org/jira/browse/ISIS-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andi Huber updated ISIS-2511:
-----------------------------
Description:
Using uniform namespaces of form
- isis.applib.*
- isis.metamodel.*
- isis.persistence.*
- isis.security.*
- isis.runtime.*
- isis.runtimeservices.*
- isis.ext.*
- isis.sub.*
- isis.tooling.*
... etc
These do not have to reflect exact Java package names nor module names, but should rather capture coarse grained structure along with easy readable semantics.
Namespaces are allowed to span multiple modules.
Namespaces should also rather be lowercase to avoid ambiguity.
Why is this relevant? Because SecMan was reworked to now base its permission model on namespaces. Which also includes wildcard support.
was:
Using uniform namespaces of form
- isis.applib.*
- isis.metamodel.*
- isis.persistence.*
- isis.security.*
- isis.runtime.*
- isis.runtimeservices.*
- isis.ext.*
- isis.sub.*
- isis.tooling.*
... etc
These do not have to reflect exact Java package names nor module names, but should rather capture coarse grained structure along with easy readable semantics.
Namespaces should also rather be lowercase to avoid ambiguity.
Why is this relevant? Because SecMan was reworked to now base its permission model on namespaces. Which also includes wildcard support.
> Rationalize all @Named("...") @DomainXxx(objectType="...") namespaces.
> ----------------------------------------------------------------------
>
> Key: ISIS-2511
> URL: https://issues.apache.org/jira/browse/ISIS-2511
> Project: Isis
> Issue Type: Improvement
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M5
>
>
> Using uniform namespaces of form
> - isis.applib.*
> - isis.metamodel.*
> - isis.persistence.*
> - isis.security.*
> - isis.runtime.*
> - isis.runtimeservices.*
> - isis.ext.*
> - isis.sub.*
> - isis.tooling.*
> ... etc
> These do not have to reflect exact Java package names nor module names, but should rather capture coarse grained structure along with easy readable semantics.
> Namespaces are allowed to span multiple modules.
> Namespaces should also rather be lowercase to avoid ambiguity.
> Why is this relevant? Because SecMan was reworked to now base its permission model on namespaces. Which also includes wildcard support.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)