You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Daniel Keir Haywood (Jira)" <ji...@apache.org> on 2021/06/17 07:31:00 UTC

[jira] [Updated] (ISIS-2748) Presence of "mustSatisfy" Specifications causes integ tests to fail .... UNKNOWN bean sort

     [ https://issues.apache.org/jira/browse/ISIS-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Keir Haywood updated ISIS-2748:
--------------------------------------
    Description: 
domainapp.modules.base.types.Name$Specification: is a (concrete) but UNKNOWN sort, yet has 3 actions: \{domainapp.modules.base.types.Name.Specification#satisfies(java.lang.Object), domainapp.modules.base.types.Name.Specification#satisfiesTranslatable(java.lang.Object), domainapp.modules.base.types.Name.Specification#satisfiesTranslatableSafely(java.lang.String)}

Moreover, this is when

isis.applib.annotation.action.explicit=true

To add insult to injury, AbstractSpecification2 does not declare @Programmatic and also declares final methods that cannot be overrridden.

  was:domainapp.modules.base.types.Name$Specification: is a (concrete) but UNKNOWN sort, yet has 3 actions: \{domainapp.modules.base.types.Name.Specification#satisfies(java.lang.Object), domainapp.modules.base.types.Name.Specification#satisfiesTranslatable(java.lang.Object), domainapp.modules.base.types.Name.Specification#satisfiesTranslatableSafely(java.lang.String)}


> Presence of "mustSatisfy" Specifications causes integ tests to fail .... UNKNOWN bean sort
> ------------------------------------------------------------------------------------------
>
>                 Key: ISIS-2748
>                 URL: https://issues.apache.org/jira/browse/ISIS-2748
>             Project: Isis
>          Issue Type: Improvement
>          Components: Isis Core
>    Affects Versions: 2.0.0-M5
>            Reporter: Daniel Keir Haywood
>            Priority: Minor
>             Fix For: 2.0.0-M6
>
>
> domainapp.modules.base.types.Name$Specification: is a (concrete) but UNKNOWN sort, yet has 3 actions: \{domainapp.modules.base.types.Name.Specification#satisfies(java.lang.Object), domainapp.modules.base.types.Name.Specification#satisfiesTranslatable(java.lang.Object), domainapp.modules.base.types.Name.Specification#satisfiesTranslatableSafely(java.lang.String)}
> Moreover, this is when
> isis.applib.annotation.action.explicit=true
> To add insult to injury, AbstractSpecification2 does not declare @Programmatic and also declares final methods that cannot be overrridden.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)