[jira] [Updated] (ISIS-3111) (Small) issues with simple/demo app... prior to m8 release
[
https://issues.apache.org/jira/browse/ISIS-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-3111:
--
Description:
{*}to fix{*}{*}{{*}}
_Object_recentAuditEntries_
choice of properties is an empty list
_session log (JPA)_
logout does not update causedby and logout timestamp. The SPI is being called,
and the entity updated, for some reason not flushed. Perhaps this is weaving
not enabled?
_empty "other" tab_
I tend to use :
!image-2022-08-04-16-18-33-740.png!
as a way to place any unreferenced properties out of the way. In v1, if there
are no unreferenced properties, then both the fieldset and the tab are
suppressed. In v2, the tab is still shown (as empty).
_in simpleapp (jpa-SNAPSHOT) ... commandDTO not showing as syntax-highlighted
XML_
missing a dependency of some sort?
in simpleapp (jpa-SNAPSHOT) ... overiding name of member in layout.xml does not
seem to work
!image-2022-08-04-15-27-48-182.png|width=475,height=99!
and yet:
!image-2022-08-04-15-28-04-365.png|width=407,height=213!
_*theming*_
in flatly theme, enabled buttons could be mistaken for being disabled - they
are rather pale. With the darkly theme, it's worse - enabled buttons
definitely do look disabled
!image-2022-08-04-11-58-16-650.png|width=495,height=227!
*fixed*
changes (at bottom) just show as toString
[https://demo-wicket.jdo.isis.incode.work/wicket/entity/demo.DomainObjectEntityChangePublishingEnabledEntity:1]
!image-2022-08-04-12-28-16-206.png|width=893,height=91!
was:
{*}to fix{*}{*}{{*}}
_session log (JPA)_
logout does not update causedby and logout timestamp. The SPI is being called,
and the entity updated, for some reason not flushed. Perhaps this is weaving
not enabled?
_empty "other" tab_
I tend to use :
!image-2022-08-04-16-18-33-740.png!
as a way to place any unreferenced properties out of the way. In v1, if there
are no unreferenced properties, then both the fieldset and the tab are
suppressed. In v2, the tab is still shown (as empty).
_in simpleapp (jpa-SNAPSHOT) ... commandDTO not showing as syntax-highlighted
XML_
missing a dependency of some sort?
in simpleapp (jpa-SNAPSHOT) ... overiding name of member in layout.xml does not
seem to work
!image-2022-08-04-15-27-48-182.png|width=475,height=99!
and yet:
!image-2022-08-04-15-28-04-365.png|width=407,height=213!
_*theming*_
in flatly theme, enabled buttons could be mistaken for being disabled - they
are rather pale. With the darkly theme, it's worse - enabled buttons
definitely do look disabled
!image-2022-08-04-11-58-16-650.png|width=495,height=227!
*fixed*
changes (at bottom) just show as toString
[https://demo-wicket.jdo.isis.incode.work/wicket/entity/demo.DomainObjectEntityChangePublishingEnabledEntity:1]
!image-2022-08-04-12-28-16-206.png|width=893,height=91!
> (Small) issues with simple/demo app... prior to m8 release
> ---
>
> Key: ISIS-3111
> URL: https://issues.apache.org/jira/browse/ISIS-3111
> Project: Isis
> Issue Type: Bug
> Components: Isis Examples Demo App
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Major
> Fix For: 2.0.0-M8
>
> Attachments: image-2022-08-04-11-57-57-001.png,
> image-2022-08-04-11-58-16-650.png, image-2022-08-04-12-28-16-206.png,
> image-2022-08-04-15-27-09-553.png, image-2022-08-04-15-27-48-182.png,
> image-2022-08-04-15-28-04-365.png, image-2022-08-04-16-18-33-740.png
>
>
> {*}to fix{*}{*}{{*}}
> _Object_recentAuditEntries_
> choice of properties is an empty list
> _session log (JPA)_
> logout does not update causedby and logout timestamp. The SPI is being
> called, and the entity updated, for some reason not flushed. Perhaps this is
> weaving not enabled?
>
> _empty "other" tab_
> I tend to use :
> !image-2022-08-04-16-18-33-740.png!
> as a way to place any unreferenced properties out of the way. In v1, if
> there are no unreferenced properties, then both the fieldset and the tab are
> suppressed. In v2, the tab is still shown (as empty).
>
> _in simpleapp (jpa-SNAPSHOT) ... commandDTO not showing as syntax-highlighted
> XML_
> missing a dependency of some sort?
>
> in simpleapp (jpa-SNAPSHOT) ... overiding name of member in layout.xml does
> not seem to work
> !image-2022-08-04-15-27-48-182.png|width=475,height=99!
>
> and yet:
>
> !image-2022-08-04-15-28-04-365.png|width=407,height=213!
>
> _*theming*_
> in flatly theme, enabled buttons could be mistaken for being disabled - they
> are rather pale. With the darkly theme, it's worse - enabled buttons
> definitely do look disabled
> !image-2022-08-04-11-58-16-650.png|width=495,height=227!
>
>
> *fixed*
> changes (at bott
[jira] [Updated] (ISIS-2646) [Project Rename] Update layout namespace (bs3->bs)
[ https://issues.apache.org/jira/browse/ISIS-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2646: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-rename) > [Project Rename] Update layout namespace (bs3->bs) > -- > > Key: ISIS-2646 > URL: https://issues.apache.org/jira/browse/ISIS-2646 > Project: Isis > Issue Type: Wish > Components: Isis Core >Reporter: Andi Huber >Priority: Major > Fix For: 2.0.0-RC1 > > Attachments: image (5).png > > > Dan: For BS3 Grid, I suggest perhaps we rename it to BSGrid or BootstrapGrid, > just remove the version from the name. Because even if in each version of > Bootstrap there are changes and improvements, I think at our level of > abstraction we don't care about that detail. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-1303) [Project Rename] Decide on a name to better describe the project's values and purpose
[ https://issues.apache.org/jira/browse/ISIS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-1303: -- Summary: [Project Rename] Decide on a name to better describe the project's values and purpose (was: [Project Rename] Rename the project to better describe its values and purpose) > [Project Rename] Decide on a name to better describe the project's values and > purpose > - > > Key: ISIS-1303 > URL: https://issues.apache.org/jira/browse/ISIS-1303 > Project: Isis > Issue Type: Wish > Components: Isis Docs & Website >Affects Versions: 1.11.1 >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-rename > > Attachments: ApacheFarthing.jpg, ApacheFarthing.jpg, > ApacheGestalt.jpg, Offset-curves-of-sinus-curve.svg > > > In the past there have been a couple of discussions regarding renaming the > project, the reason generally cited being the potential embarrassment of > sharing a name with the jihadist militant group [1] currently prominent in > the headlines. After due discussion on the mailing lists the prevailing view > has been to retain our name: "we were here first". > Until now I've concurred with that view also... after all, I originally came > up with the name "Isis", originally based on the name of the Thames as it > flows through Oxford [2] (many of the original authors of the framework live > within Oxfordshire, UK). > Separately to that discussion, we have the issue of marketing. Originally we > marketed ourselves as a framework implementing the "naked objects" pattern > [3]; the original name of the framework (prior to Apache) was of course the > Naked Objects Framework. However, this pattern is either not well-known or > is misunderstood (only a low proportion of developers that encounter the idea > immediately "get it"). The crudity of the original user interfaces didn't > help. And the name also, of course, can cause embarrassment in some cultures. > Then, when domain-driven design [4] came along as a movement, that seemed an > obvious platform upon which to position the framework: we obviously share the > core belief that the domain is the most important bit of the system. However > - and I still find this surprising - despite attempts otherwise we haven't > really made too much of an impression in that community. The fact that the > DDD community got massively sidetracked for a while by the CQRS pattern is > perhaps part of it. I also often detect the view that DDD should imply not > using a framework. The irony of course is that in rejecting framework such > developers actually have to write more infrastructure code vs business domain > code. > Also, the fit is perhaps not all that good after all. In the DDD community I > don't see anyone talking about modules... one of the named patterns, and a > major focus of our framework, but missing from DDD talks. Instead they get > side-tracked talking only about aggregate roots or bounded contexts; all well > and good, but over-emphasised). > [Aside: Indeed, I raised the topic of modules with Eric Evans himself (in > person), and he agreed there was little emphasis. When I described our > framework's use of domain events to hook modules together (along with vetoing > behaviour we support) he admitted it was a new approach/pattern to him...] > Anyway, so DDD - which looked so promising - hasn't delivered. They might > come around to us one day, but it's probably time to define our own > individual space. Also, in the same way that everyone takes agile > development for granted as the "de facto", we ought to simply take DDD for > granted too... "of course you will be doing DDD, but are you doing it well?" > What we need to better market the framework is some other pattern or concept > or hook, and become known as the framework that best supports that idea. > There are several candidates: > - hexagonal architecture (also called ports and adapters, or the onion > architecture, and related to the clean architecture) > - don't repeat yourself principle > - aspect oriented programming (naked objects pattern is really the > recognition that UI presentation is a cross-cutting concern) > - the general concept of modularity > - DCI (data/context/interactions). > - "clean" "pure" "essential" pojo programming model > - agile, lean > - breaking down barriers between IT and business > Of these, I think that hexagonal architecture looks the best fit; it is well > regarded as a concept among the "cognoscenti", but there are surprisingly no > open source frameworks out there (at least in the Java space) that position > themselves as being the natural choice. > Therefore, I think a name - and appropri
[jira] [Closed] (ISIS-1303) [Project Rename] Decide on a name to better describe the project's values and purpose
[ https://issues.apache.org/jira/browse/ISIS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood closed ISIS-1303. - Assignee: Daniel Keir Haywood > [Project Rename] Decide on a name to better describe the project's values and > purpose > - > > Key: ISIS-1303 > URL: https://issues.apache.org/jira/browse/ISIS-1303 > Project: Isis > Issue Type: Wish > Components: Isis Docs & Website >Affects Versions: 1.11.1 >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > Attachments: ApacheFarthing.jpg, ApacheFarthing.jpg, > ApacheGestalt.jpg, Offset-curves-of-sinus-curve.svg > > > In the past there have been a couple of discussions regarding renaming the > project, the reason generally cited being the potential embarrassment of > sharing a name with the jihadist militant group [1] currently prominent in > the headlines. After due discussion on the mailing lists the prevailing view > has been to retain our name: "we were here first". > Until now I've concurred with that view also... after all, I originally came > up with the name "Isis", originally based on the name of the Thames as it > flows through Oxford [2] (many of the original authors of the framework live > within Oxfordshire, UK). > Separately to that discussion, we have the issue of marketing. Originally we > marketed ourselves as a framework implementing the "naked objects" pattern > [3]; the original name of the framework (prior to Apache) was of course the > Naked Objects Framework. However, this pattern is either not well-known or > is misunderstood (only a low proportion of developers that encounter the idea > immediately "get it"). The crudity of the original user interfaces didn't > help. And the name also, of course, can cause embarrassment in some cultures. > Then, when domain-driven design [4] came along as a movement, that seemed an > obvious platform upon which to position the framework: we obviously share the > core belief that the domain is the most important bit of the system. However > - and I still find this surprising - despite attempts otherwise we haven't > really made too much of an impression in that community. The fact that the > DDD community got massively sidetracked for a while by the CQRS pattern is > perhaps part of it. I also often detect the view that DDD should imply not > using a framework. The irony of course is that in rejecting framework such > developers actually have to write more infrastructure code vs business domain > code. > Also, the fit is perhaps not all that good after all. In the DDD community I > don't see anyone talking about modules... one of the named patterns, and a > major focus of our framework, but missing from DDD talks. Instead they get > side-tracked talking only about aggregate roots or bounded contexts; all well > and good, but over-emphasised). > [Aside: Indeed, I raised the topic of modules with Eric Evans himself (in > person), and he agreed there was little emphasis. When I described our > framework's use of domain events to hook modules together (along with vetoing > behaviour we support) he admitted it was a new approach/pattern to him...] > Anyway, so DDD - which looked so promising - hasn't delivered. They might > come around to us one day, but it's probably time to define our own > individual space. Also, in the same way that everyone takes agile > development for granted as the "de facto", we ought to simply take DDD for > granted too... "of course you will be doing DDD, but are you doing it well?" > What we need to better market the framework is some other pattern or concept > or hook, and become known as the framework that best supports that idea. > There are several candidates: > - hexagonal architecture (also called ports and adapters, or the onion > architecture, and related to the clean architecture) > - don't repeat yourself principle > - aspect oriented programming (naked objects pattern is really the > recognition that UI presentation is a cross-cutting concern) > - the general concept of modularity > - DCI (data/context/interactions). > - "clean" "pure" "essential" pojo programming model > - agile, lean > - breaking down barriers between IT and business > Of these, I think that hexagonal architecture looks the best fit; it is well > regarded as a concept among the "cognoscenti", but there are surprisingly no > open source frameworks out there (at least in the Java space) that position > themselves as being the natural choice. > Therefore, I think a name - and appropriate short tag line - based around > this idea of hexagonal architecture should be considered. > Candidate names: >
[jira] [Resolved] (ISIS-1303) [Project Rename] Decide on a name to better describe the project's values and purpose
[ https://issues.apache.org/jira/browse/ISIS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood resolved ISIS-1303. --- Fix Version/s: 2.0.0-M8 (was: 2.0.0-rename) Resolution: Fixed We have voted to rename to CAUSEWAY https://lists.apache.org/thread/g2zkhyt57noodsry22lcznd10yo7hk5t > [Project Rename] Decide on a name to better describe the project's values and > purpose > - > > Key: ISIS-1303 > URL: https://issues.apache.org/jira/browse/ISIS-1303 > Project: Isis > Issue Type: Wish > Components: Isis Docs & Website >Affects Versions: 1.11.1 >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > Attachments: ApacheFarthing.jpg, ApacheFarthing.jpg, > ApacheGestalt.jpg, Offset-curves-of-sinus-curve.svg > > > In the past there have been a couple of discussions regarding renaming the > project, the reason generally cited being the potential embarrassment of > sharing a name with the jihadist militant group [1] currently prominent in > the headlines. After due discussion on the mailing lists the prevailing view > has been to retain our name: "we were here first". > Until now I've concurred with that view also... after all, I originally came > up with the name "Isis", originally based on the name of the Thames as it > flows through Oxford [2] (many of the original authors of the framework live > within Oxfordshire, UK). > Separately to that discussion, we have the issue of marketing. Originally we > marketed ourselves as a framework implementing the "naked objects" pattern > [3]; the original name of the framework (prior to Apache) was of course the > Naked Objects Framework. However, this pattern is either not well-known or > is misunderstood (only a low proportion of developers that encounter the idea > immediately "get it"). The crudity of the original user interfaces didn't > help. And the name also, of course, can cause embarrassment in some cultures. > Then, when domain-driven design [4] came along as a movement, that seemed an > obvious platform upon which to position the framework: we obviously share the > core belief that the domain is the most important bit of the system. However > - and I still find this surprising - despite attempts otherwise we haven't > really made too much of an impression in that community. The fact that the > DDD community got massively sidetracked for a while by the CQRS pattern is > perhaps part of it. I also often detect the view that DDD should imply not > using a framework. The irony of course is that in rejecting framework such > developers actually have to write more infrastructure code vs business domain > code. > Also, the fit is perhaps not all that good after all. In the DDD community I > don't see anyone talking about modules... one of the named patterns, and a > major focus of our framework, but missing from DDD talks. Instead they get > side-tracked talking only about aggregate roots or bounded contexts; all well > and good, but over-emphasised). > [Aside: Indeed, I raised the topic of modules with Eric Evans himself (in > person), and he agreed there was little emphasis. When I described our > framework's use of domain events to hook modules together (along with vetoing > behaviour we support) he admitted it was a new approach/pattern to him...] > Anyway, so DDD - which looked so promising - hasn't delivered. They might > come around to us one day, but it's probably time to define our own > individual space. Also, in the same way that everyone takes agile > development for granted as the "de facto", we ought to simply take DDD for > granted too... "of course you will be doing DDD, but are you doing it well?" > What we need to better market the framework is some other pattern or concept > or hook, and become known as the framework that best supports that idea. > There are several candidates: > - hexagonal architecture (also called ports and adapters, or the onion > architecture, and related to the clean architecture) > - don't repeat yourself principle > - aspect oriented programming (naked objects pattern is really the > recognition that UI presentation is a cross-cutting concern) > - the general concept of modularity > - DCI (data/context/interactions). > - "clean" "pure" "essential" pojo programming model > - agile, lean > - breaking down barriers between IT and business > Of these, I think that hexagonal architecture looks the best fit; it is well > regarded as a concept among the "cognoscenti", but there are surprisingly no > open source frameworks out there (at least in the Java space) that position > themselves as being the natural choice. > Therefore, I think a name -
[jira] [Created] (ISIS-3130) Umbrella to rename project to CAUSEWAY
Daniel Keir Haywood created ISIS-3130: - Summary: Umbrella to rename project to CAUSEWAY Key: ISIS-3130 URL: https://issues.apache.org/jira/browse/ISIS-3130 Project: Isis Issue Type: Umbrella Reporter: Daniel Keir Haywood Assignee: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3131) Name choices, discussion, shortlist
Daniel Keir Haywood created ISIS-3131: - Summary: Name choices, discussion, shortlist Key: ISIS-3131 URL: https://issues.apache.org/jira/browse/ISIS-3131 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Assignee: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3132) Trademark search for 'Causeway'
Daniel Keir Haywood created ISIS-3132: - Summary: Trademark search for 'Causeway' Key: ISIS-3132 URL: https://issues.apache.org/jira/browse/ISIS-3132 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Assignee: Daniel Keir Haywood -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3133) PMC approval for 'Causeway'
[ https://issues.apache.org/jira/browse/ISIS-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3133: -- Fix Version/s: 2.0.0-rename > PMC approval for 'Causeway' > --- > > Key: ISIS-3133 > URL: https://issues.apache.org/jira/browse/ISIS-3133 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-rename > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3133) PMC approval for 'Causeway'
Daniel Keir Haywood created ISIS-3133: - Summary: PMC approval for 'Causeway' Key: ISIS-3133 URL: https://issues.apache.org/jira/browse/ISIS-3133 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Assignee: Daniel Keir Haywood -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3132) Trademark search for 'Causeway'
[ https://issues.apache.org/jira/browse/ISIS-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3132: -- Fix Version/s: 2.0.0-rename > Trademark search for 'Causeway' > --- > > Key: ISIS-3132 > URL: https://issues.apache.org/jira/browse/ISIS-3132 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-rename > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3134) Board approval for 'Causeway'
Daniel Keir Haywood created ISIS-3134: - Summary: Board approval for 'Causeway' Key: ISIS-3134 URL: https://issues.apache.org/jira/browse/ISIS-3134 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Assignee: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ISIS-3110) Defer audit trail publishing until end of transaction
[ https://issues.apache.org/jira/browse/ISIS-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood closed ISIS-3110. - Resolution: Fixed > Defer audit trail publishing until end of transaction > - > > Key: ISIS-3110 > URL: https://issues.apache.org/jira/browse/ISIS-3110 > Project: Isis > Issue Type: Improvement >Affects Versions: 2.0.0-M7 >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-M8 > > > The current "light-weight" implementation (introduced in ISIS-2826) would > seem to be a little too eager : when combined with the commandlog > implementation - that flushes later on - i believe we are corrupting the > internal UoW caches within EntityManager... it thinks that the id of > AuditEntry's already persisted are being updated. > The situation and error found is similar to > [https://bugs.eclipse.org/bugs/show_bug.cgi?id=333977.] > So instead, defer the actual publishing until the end, the same way that JDO > works. But still leverage the property change records that JPA provides. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3135) Various (small) issues noticed with simple/demo app...
Daniel Keir Haywood created ISIS-3135: - Summary: Various (small) issues noticed with simple/demo app... Key: ISIS-3135 URL: https://issues.apache.org/jira/browse/ISIS-3135 Project: Isis Issue Type: Bug Reporter: Daniel Keir Haywood Assignee: Daniel Keir Haywood Fix For: 2.0.0-RC1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3135) Various (small) issues noticed with simple/demo app...
[ https://issues.apache.org/jira/browse/ISIS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3135: -- Description: _Object_recentAuditEntries_ choice of properties is an empty list _session log (JPA)_ logout does not update causedby and logout timestamp. The SPI is being called, and the entity updated, for some reason not flushed. Perhaps this is weaving not enabled? _empty "other" tab_ I tend to use : !image-2022-08-04-16-18-33-740.png! as a way to place any unreferenced properties out of the way. In v1, if there are no unreferenced properties, then both the fieldset and the tab are suppressed. In v2, the tab is still shown (as empty). _in simpleapp (jpa-SNAPSHOT) ... commandDTO not showing as syntax-highlighted XML_ missing a dependency of some sort? in simpleapp (jpa-SNAPSHOT) ... overiding name of member in layout.xml does not seem to work !image-2022-08-04-15-27-48-182.png|width=475,height=99! and yet: !image-2022-08-04-15-28-04-365.png|width=407,height=213! _*theming*_ in flatly theme, enabled buttons could be mistaken for being disabled - they are rather pale. With the darkly theme, it's worse - enabled buttons definitely do look disabled !image-2022-08-04-11-58-16-650.png|width=495,height=227! > Various (small) issues noticed with simple/demo app... > > > Key: ISIS-3135 > URL: https://issues.apache.org/jira/browse/ISIS-3135 > Project: Isis > Issue Type: Bug >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-RC1 > > > _Object_recentAuditEntries_ > choice of properties is an empty list > _session log (JPA)_ > logout does not update causedby and logout timestamp. The SPI is being > called, and the entity updated, for some reason not flushed. Perhaps this is > weaving not enabled? > > _empty "other" tab_ > I tend to use : > !image-2022-08-04-16-18-33-740.png! > as a way to place any unreferenced properties out of the way. In v1, if > there are no unreferenced properties, then both the fieldset and the tab are > suppressed. In v2, the tab is still shown (as empty). > > _in simpleapp (jpa-SNAPSHOT) ... commandDTO not showing as syntax-highlighted > XML_ > missing a dependency of some sort? > > in simpleapp (jpa-SNAPSHOT) ... overiding name of member in layout.xml does > not seem to work > !image-2022-08-04-15-27-48-182.png|width=475,height=99! > > and yet: > > !image-2022-08-04-15-28-04-365.png|width=407,height=213! > > _*theming*_ > in flatly theme, enabled buttons could be mistaken for being disabled - they > are rather pale. With the darkly theme, it's worse - enabled buttons > definitely do look disabled > !image-2022-08-04-11-58-16-650.png|width=495,height=227! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3111) Pretty rendering for ChangesDto
[ https://issues.apache.org/jira/browse/ISIS-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3111: -- Summary: Pretty rendering for ChangesDto (was: (Small) issues with simple/demo app... prior to m8 release) > Pretty rendering for ChangesDto > --- > > Key: ISIS-3111 > URL: https://issues.apache.org/jira/browse/ISIS-3111 > Project: Isis > Issue Type: Bug > Components: Isis Examples Demo App >Reporter: Daniel Keir Haywood >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M8 > > Attachments: image-2022-08-04-11-57-57-001.png, > image-2022-08-04-11-58-16-650.png, image-2022-08-04-12-28-16-206.png, > image-2022-08-04-15-27-09-553.png, image-2022-08-04-15-27-48-182.png, > image-2022-08-04-15-28-04-365.png, image-2022-08-04-16-18-33-740.png > > > changes (at bottom) just show as toString > [https://demo-wicket.jdo.isis.incode.work/wicket/entity/demo.DomainObjectEntityChangePublishingEnabledEntity:1] > !image-2022-08-04-12-28-16-206.png|width=893,height=91! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3111) (Small) issues with simple/demo app... prior to m8 release
[
https://issues.apache.org/jira/browse/ISIS-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-3111:
--
Description:
changes (at bottom) just show as toString
[https://demo-wicket.jdo.isis.incode.work/wicket/entity/demo.DomainObjectEntityChangePublishingEnabledEntity:1]
!image-2022-08-04-12-28-16-206.png|width=893,height=91!
was:
{*}to fix{*}{*}{{*}}
_Object_recentAuditEntries_
choice of properties is an empty list
_session log (JPA)_
logout does not update causedby and logout timestamp. The SPI is being called,
and the entity updated, for some reason not flushed. Perhaps this is weaving
not enabled?
_empty "other" tab_
I tend to use :
!image-2022-08-04-16-18-33-740.png!
as a way to place any unreferenced properties out of the way. In v1, if there
are no unreferenced properties, then both the fieldset and the tab are
suppressed. In v2, the tab is still shown (as empty).
_in simpleapp (jpa-SNAPSHOT) ... commandDTO not showing as syntax-highlighted
XML_
missing a dependency of some sort?
in simpleapp (jpa-SNAPSHOT) ... overiding name of member in layout.xml does not
seem to work
!image-2022-08-04-15-27-48-182.png|width=475,height=99!
and yet:
!image-2022-08-04-15-28-04-365.png|width=407,height=213!
_*theming*_
in flatly theme, enabled buttons could be mistaken for being disabled - they
are rather pale. With the darkly theme, it's worse - enabled buttons
definitely do look disabled
!image-2022-08-04-11-58-16-650.png|width=495,height=227!
*fixed*
changes (at bottom) just show as toString
[https://demo-wicket.jdo.isis.incode.work/wicket/entity/demo.DomainObjectEntityChangePublishingEnabledEntity:1]
!image-2022-08-04-12-28-16-206.png|width=893,height=91!
> (Small) issues with simple/demo app... prior to m8 release
> ---
>
> Key: ISIS-3111
> URL: https://issues.apache.org/jira/browse/ISIS-3111
> Project: Isis
> Issue Type: Bug
> Components: Isis Examples Demo App
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Major
> Fix For: 2.0.0-M8
>
> Attachments: image-2022-08-04-11-57-57-001.png,
> image-2022-08-04-11-58-16-650.png, image-2022-08-04-12-28-16-206.png,
> image-2022-08-04-15-27-09-553.png, image-2022-08-04-15-27-48-182.png,
> image-2022-08-04-15-28-04-365.png, image-2022-08-04-16-18-33-740.png
>
>
> changes (at bottom) just show as toString
> [https://demo-wicket.jdo.isis.incode.work/wicket/entity/demo.DomainObjectEntityChangePublishingEnabledEntity:1]
> !image-2022-08-04-12-28-16-206.png|width=893,height=91!
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ISIS-3111) Pretty rendering for ChangesDto
[ https://issues.apache.org/jira/browse/ISIS-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood resolved ISIS-3111. --- Resolution: Fixed > Pretty rendering for ChangesDto > --- > > Key: ISIS-3111 > URL: https://issues.apache.org/jira/browse/ISIS-3111 > Project: Isis > Issue Type: Bug > Components: Isis Examples Demo App >Reporter: Daniel Keir Haywood >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M8 > > Attachments: image-2022-08-04-11-57-57-001.png, > image-2022-08-04-11-58-16-650.png, image-2022-08-04-12-28-16-206.png, > image-2022-08-04-15-27-09-553.png, image-2022-08-04-15-27-48-182.png, > image-2022-08-04-15-28-04-365.png, image-2022-08-04-16-18-33-740.png > > > changes (at bottom) just show as toString > [https://demo-wicket.jdo.isis.incode.work/wicket/entity/demo.DomainObjectEntityChangePublishingEnabledEntity:1] > !image-2022-08-04-12-28-16-206.png|width=893,height=91! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ISIS-3111) (Small) issues with simple/demo app... prior to m8 release
[ https://issues.apache.org/jira/browse/ISIS-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood reassigned ISIS-3111: - Assignee: Andi Huber (was: Daniel Keir Haywood) > (Small) issues with simple/demo app... prior to m8 release > --- > > Key: ISIS-3111 > URL: https://issues.apache.org/jira/browse/ISIS-3111 > Project: Isis > Issue Type: Bug > Components: Isis Examples Demo App >Reporter: Daniel Keir Haywood >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M8 > > Attachments: image-2022-08-04-11-57-57-001.png, > image-2022-08-04-11-58-16-650.png, image-2022-08-04-12-28-16-206.png, > image-2022-08-04-15-27-09-553.png, image-2022-08-04-15-27-48-182.png, > image-2022-08-04-15-28-04-365.png, image-2022-08-04-16-18-33-740.png > > > changes (at bottom) just show as toString > [https://demo-wicket.jdo.isis.incode.work/wicket/entity/demo.DomainObjectEntityChangePublishingEnabledEntity:1] > !image-2022-08-04-12-28-16-206.png|width=893,height=91! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-2947) GraphQL viewer
[ https://issues.apache.org/jira/browse/ISIS-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2947: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) > GraphQL viewer > -- > > Key: ISIS-2947 > URL: https://issues.apache.org/jira/browse/ISIS-2947 > Project: Isis > Issue Type: New Feature > Components: Isis Viewer GraphQL >Reporter: Daniel Keir Haywood >Assignee: Johan Doornenbal >Priority: Major > Fix For: 2.0.0-RC1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-2873) petclinic tutorial (documentation)
[ https://issues.apache.org/jira/browse/ISIS-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2873: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) > petclinic tutorial (documentation) > --- > > Key: ISIS-2873 > URL: https://issues.apache.org/jira/browse/ISIS-2873 > Project: Isis > Issue Type: New Feature >Affects Versions: 2.0.0-M6 >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-RC1 > > > convert over gitlab.com/danhaywood/isis-petclinic-tutorial-docs, also use > isis-app-demo as the companion repo. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-2844) With Secman, SudoService behaves differently from impersonation - should be consistent.
[ https://issues.apache.org/jira/browse/ISIS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2844: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) Description: _*Analysis:*_ when sudo service runs and secman is configured, the effective permissions are obtained from the ApplicationUser object, and whichever ApplicationRoles that ApplicationUser happens to have. in contrast, when impersonating then the permissions are obtained from the UserMemento + associated RoleMementos. For consistency, I think that sudo service should also use the UserMemento to obtain the roles in effect. (Note: if not running under sudo service and not impersonating, then we also use the roles from usermemento; but these would have been copied from the ApplicatoinUser on login). In terms of change to the user experience, because a `UserMemento` is immutable and is only populated on login from the `ApplicationUser`, and that it contains the roles, then the user will need to logout and login if they are added to any new roles while logged in. I think this is acceptable. ~~~ _*Implementation:*_ In terms of code, it's pretty trivial I think; we just remove the check for userService.isImpersonating() below and always run the first branch, ie query `byUserMemento(...)`. The `byUser(...)` method is probably therefore redundant and could be removed. See code snippet below. !image-2021-08-18-16-24-04-978.png|width=879,height=376! was: I think that permissions should always be taken from the usermemento. For the three use cases: * impersonation (as already is case): we use the roles specified on the usermemento * sudo service (new code): we instead use the roles specified on the usermemento * no sudoservice, no impersonation : we obtain the roles from the usermemento, which would have been copied from the ApplicationUser on login. In terms of code, I think we just remove the check for userService.isImpersonating() below and always run the first branch, ie query `byUserMemento(...)`. The `byUser(...)` method is probably therefore redundant and could be removed. See code snippet below. In terms of change to the user experience, because a `UserMemento` is immutable and is only populated on login from the `ApplicationUser`, and that it contains the roles, then the user will need to logout and login if they are added to any new roles while logged in. I think this is acceptable. !image-2021-08-18-16-24-04-978.png|width=879,height=376! > With Secman, SudoService behaves differently from impersonation - should be > consistent. > --- > > Key: ISIS-2844 > URL: https://issues.apache.org/jira/browse/ISIS-2844 > Project: Isis > Issue Type: Improvement > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M6 >Reporter: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-RC1 > > Attachments: image-2021-08-18-16-24-04-978.png > > > _*Analysis:*_ > when sudo service runs and secman is configured, the effective permissions > are obtained from the ApplicationUser object, and whichever ApplicationRoles > that ApplicationUser happens to have. > in contrast, when impersonating then the permissions are obtained from the > UserMemento + associated RoleMementos. > For consistency, I think that sudo service should also use the UserMemento to > obtain the roles in effect. > (Note: if not running under sudo service and not impersonating, then we also > use the roles from usermemento; but these would have been copied from the > ApplicatoinUser on login). > In terms of change to the user experience, because a `UserMemento` is > immutable and is only populated on login from the `ApplicationUser`, and that > it contains the roles, then the user will need to logout and login if they > are added to any new roles while logged in. I think this is acceptable. > ~~~ > _*Implementation:*_ > In terms of code, it's pretty trivial I think; we just remove the check for > userService.isImpersonating() below and always run the first branch, ie query > `byUserMemento(...)`. The `byUser(...)` method is probably therefore > redundant and could be removed. See code snippet below. > !image-2021-08-18-16-24-04-978.png|width=879,height=376! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3030) Multiple level drop down List issue
[
https://issues.apache.org/jira/browse/ISIS-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-3030:
--
Fix Version/s: 2.0.0-RC1
(was: 2.0.0-M8)
> Multiple level drop down List issue
> ---
>
> Key: ISIS-3030
> URL: https://issues.apache.org/jira/browse/ISIS-3030
> Project: Isis
> Issue Type: Bug
> Components: Isis Applib (programming model)
>Reporter: Han Hui Wen
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> Here has a mulitiple level drop down list.
>
>
> {code:java}
> @Property(editing = Editing.ENABLED)
> @Getter
> @Setter
> private String tc1Name;
> @Property(editing = Editing.ENABLED)
> @Getter
> @Setter
> private String tc2Name;
> @Property(editing = Editing.ENABLED)
> @Getter
> @Setter
> private String tc3Name;
> @Property(editing = Editing.ENABLED)
> @Getter
> @Setter
> private String tc4Name;
> public List choices0Create() {
> List list = tc1ObjectRepo.findAll();
> List nameList = list.stream().map(i ->
> i.getTechCapabL1Name()).
> distinct().collect(Collectors.toList());
> return nameList;
> }
> public String default0Create() {
> return getTc1Name();
> }
> public List choices1Create(String tc1Name) {
> System.out.println("tc1Name: " + tc1Name);
> Tc1Object tc1 = tc1ObjectRepo.findByTechCapabL1Name(tc1Name);
> System.out.println("tc1: " + tc1);
> List list = tc2ObjectRepo.findByTc1Object(tc1);
> List nameList = list.stream().map(i ->
> i.getTechCapabL2Name()).
>distinct().collect(Collectors.toList());
> return nameList;
> }
> public String default1Create() {
> return getTc2Name();
> }
> public List choices2Create(String tc2Name) {
> System.out.println("tc2Name: " + tc2Name);
> Tc2Object tc2 = tc2ObjectRepo.findByTechCapabL2Name(tc2Name);
> System.out.println("tc2: " + tc2);
> List list = tc3ObjectRepo.findByTc2Object(tc2);
> System.out.println("tc list :" + list);
> List nameList = list.stream().map(i ->
>i.getTechCapabL3Name()).distinct().
>collect(Collectors.toList());
> return nameList;
> }
> public String default2Create() {
> return getTc3Name();
> }
> public List choices3Create(String tc3Name) {
> Tc3Object tc3 = tc3ObjectRepo.findByTechCapabL3Name(tc3Name);
> List list = tc4ObjectRepo.findByTc3Object(tc3);
> List nameList = list.stream().map(i ->
> i.getTechCapabL4Name()).distinct().
> collect(Collectors.toList());
> return nameList;
> }
> public String default3Create() {
> return getTc4Name();
> }
>
> @Action(semantics = SemanticsOf.NON_IDEMPOTENT)
> @ActionLayout(promptStyle = PromptStyle.DIALOG_MODAL)
> public CtlgObject create(
> final String tc1Name,
> final String tc2Name,
> final String tc3Name,
> final String tc4Name,
>
> final String baseTechName)
> {
> setTc1Name(tc1Name);
> setTc2Name(tc2Name);
> setTc3Name(tc3Name);
> setTc4Name(tc4Name);
> return repositoryService.persist(new CtlgObject(tc1Name,
> tc2Name, tc3Name, tc4Name, baseTechName));
> } {code}
>
>
> -
> in choices2Create(String tc2Name) function , value of tc2Name is equal
> tc1Name ,it's equal the first drop dwon list value ,not the second drop down
> list value .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ISIS-2868) archtest jpa - @DiscriminatorValue and logicalTypeName
[ https://issues.apache.org/jira/browse/ISIS-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2868: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) > archtest jpa - @DiscriminatorValue and logicalTypeName > -- > > Key: ISIS-2868 > URL: https://issues.apache.org/jira/browse/ISIS-2868 > Project: Isis > Issue Type: Improvement >Affects Versions: 2.0.0-M6 >Reporter: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-RC1 > > > https://vladmihalcea.com/the-best-way-to-map-the-discriminatorcolumn-with-jpa-and-hibernate/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3081) Check for existence of feature in fixturescript
[ https://issues.apache.org/jira/browse/ISIS-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3081: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) > Check for existence of feature in fixturescript > --- > > Key: ISIS-3081 > URL: https://issues.apache.org/jira/browse/ISIS-3081 > Project: Isis > Issue Type: Improvement > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M8 >Reporter: Patrick Deenen >Priority: Major > Fix For: 2.0.0-RC1 > > > When one defines a fixture based on AbstractRoleAndPermissionsFixtureScript > using newPermissions NO check is done if the new permission is actually > referring to an actual valid feature. Hence it is possible to define > permissions that have no effect or have no effect. So it would be better to > at least check is the member exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3075) Throwing an IllegalArgumentException should display ErrorPage
[ https://issues.apache.org/jira/browse/ISIS-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3075: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) > Throwing an IllegalArgumentException should display ErrorPage > - > > Key: ISIS-3075 > URL: https://issues.apache.org/jira/browse/ISIS-3075 > Project: Isis > Issue Type: Bug > Components: Isis Persistence JPA, Isis Viewer Wicket >Affects Versions: 2.0.0-M7 > Environment: JPA >Reporter: Martin Hesse >Priority: Major > Fix For: 2.0.0-RC1 > > Attachments: image-2022-06-13-23-48-56-870.png, > image-2022-06-13-23-50-44-870.png > > > This can be reproduced using the demo of the Error Reporting Service in the > JPA demo app. When clicking on the button "Trigger an Error" a red message is > shown saying "invalid data access api usage": > !image-2022-06-13-23-48-56-870.png! > Instead it should show the viewer error page with the details of the custom > EmailTicket returned by the ErrorReportingServiceDemoImplementation > implementation. > When changing the IllegalArgumentException to a NullPointerException it works > as expected: > !image-2022-06-13-23-50-44-870.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3079) Secman should provide a convenience role to allow fixture scripts to be run.
[ https://issues.apache.org/jira/browse/ISIS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3079: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) > Secman should provide a convenience role to allow fixture scripts to be run. > > > Key: ISIS-3079 > URL: https://issues.apache.org/jira/browse/ISIS-3079 > Project: Isis > Issue Type: Improvement > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M7 >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-RC1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ISIS-3117) Add missing sha256 or sha512 to already released isis/isis-parent/isis-parent-2.0.0-M7-source-release.zip
[ https://issues.apache.org/jira/browse/ISIS-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582171#comment-17582171 ] Daniel Keir Haywood commented on ISIS-3117: --- Probably won't do this, but to double check that the m8 version does generate them ok... > Add missing sha256 or sha512 to already released > isis/isis-parent/isis-parent-2.0.0-M7-source-release.zip > - > > Key: ISIS-3117 > URL: https://issues.apache.org/jira/browse/ISIS-3117 > Project: Isis > Issue Type: Task > Components: Isis CI & Build Scripts >Affects Versions: 2.0.0-M7 >Reporter: Andi Huber >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ISIS-3117) Add missing sha256 or sha512 to already released isis/isis-parent/isis-parent-2.0.0-M7-source-release.zip
[ https://issues.apache.org/jira/browse/ISIS-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood reassigned ISIS-3117: - Assignee: Daniel Keir Haywood > Add missing sha256 or sha512 to already released > isis/isis-parent/isis-parent-2.0.0-M7-source-release.zip > - > > Key: ISIS-3117 > URL: https://issues.apache.org/jira/browse/ISIS-3117 > Project: Isis > Issue Type: Task > Components: Isis CI & Build Scripts >Affects Versions: 2.0.0-M7 >Reporter: Andi Huber >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ISIS-3041) [Ongoing] Site/Doc Maintenance
[ https://issues.apache.org/jira/browse/ISIS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582174#comment-17582174 ] Daniel Keir Haywood commented on ISIS-3041: --- I'm moving this back to m8, so I can merge its branch in (there is just one doc fix on a branch) and then close the ticket as done. Please raise a new ticket for the next release's doc fixes. > [Ongoing] Site/Doc Maintenance > -- > > Key: ISIS-3041 > URL: https://issues.apache.org/jira/browse/ISIS-3041 > Project: Isis > Issue Type: Documentation > Components: Isis Docs & Website >Reporter: Jörg Rade >Assignee: Andi Huber >Priority: Minor > Fix For: 2.0.0-RC1 > > > Ongoing task across releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3041) [Ongoing] Site/Doc Maintenance
[ https://issues.apache.org/jira/browse/ISIS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3041: -- Fix Version/s: 2.0.0-M8 (was: 2.0.0-RC1) > [Ongoing] Site/Doc Maintenance > -- > > Key: ISIS-3041 > URL: https://issues.apache.org/jira/browse/ISIS-3041 > Project: Isis > Issue Type: Documentation > Components: Isis Docs & Website >Reporter: Jörg Rade >Assignee: Andi Huber >Priority: Minor > Fix For: 2.0.0-M8 > > > Ongoing task across releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ISIS-3041) [Ongoing] Site/Doc Maintenance
[ https://issues.apache.org/jira/browse/ISIS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood resolved ISIS-3041. --- Resolution: Fixed > [Ongoing] Site/Doc Maintenance > -- > > Key: ISIS-3041 > URL: https://issues.apache.org/jira/browse/ISIS-3041 > Project: Isis > Issue Type: Documentation > Components: Isis Docs & Website >Reporter: Jörg Rade >Assignee: Andi Huber >Priority: Minor > Fix For: 2.0.0-M8 > > > Ongoing task across releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-2678) Add missing documentation to explain the Parameters syntax for dependent (mixin) action args.
[ https://issues.apache.org/jira/browse/ISIS-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2678: -- Component/s: Isis Docs & Website > Add missing documentation to explain the Parameters syntax for dependent > (mixin) action args. > - > > Key: ISIS-2678 > URL: https://issues.apache.org/jira/browse/ISIS-2678 > Project: Isis > Issue Type: Documentation > Components: Isis Docs & Website >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-RC1 > > > as per slack: > [https://the-asf.slack.com/archives/CFC42LWBV/p1620978920239500?thread_ts=1620833729.210100&cid=CFC42LWBV] > We should backport this to the current website. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-2678) Add missing documentation to explain the Parameters syntax for dependent (mixin) action args.
[ https://issues.apache.org/jira/browse/ISIS-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2678: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) > Add missing documentation to explain the Parameters syntax for dependent > (mixin) action args. > - > > Key: ISIS-2678 > URL: https://issues.apache.org/jira/browse/ISIS-2678 > Project: Isis > Issue Type: Documentation >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-RC1 > > > as per slack: > [https://the-asf.slack.com/archives/CFC42LWBV/p1620978920239500?thread_ts=1620833729.210100&cid=CFC42LWBV] > We should backport this to the current website. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-2832) Add Docs for @Property(entityChangePublishing=...)
[ https://issues.apache.org/jira/browse/ISIS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2832: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) > Add Docs for @Property(entityChangePublishing=...) > -- > > Key: ISIS-2832 > URL: https://issues.apache.org/jira/browse/ISIS-2832 > Project: Isis > Issue Type: Improvement > Components: Isis Docs & Website >Reporter: Andi Huber >Priority: Minor > Fix For: 2.0.0-RC1 > > > as a follow up on https://issues.apache.org/jira/browse/ISIS-2490 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ISIS-2858) AbstractUserAndRoleScript and similar should inject into suppliers.
[ https://issues.apache.org/jira/browse/ISIS-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood reassigned ISIS-2858: - Assignee: Daniel Keir Haywood > AbstractUserAndRoleScript and similar should inject into suppliers. > --- > > Key: ISIS-2858 > URL: https://issues.apache.org/jira/browse/ISIS-2858 > Project: Isis > Issue Type: Improvement > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M6 >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-M8 > > > Or alternatively, rather than pass into the constructor, could provide hook > methods to return the values? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-2505) [kroviz] Catch Up With Demo Examples
[ https://issues.apache.org/jira/browse/ISIS-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2505: -- Fix Version/s: 2.0.0-RC1 (was: 2.0.0-M8) > [kroviz] Catch Up With Demo Examples > > > Key: ISIS-2505 > URL: https://issues.apache.org/jira/browse/ISIS-2505 > Project: Isis > Issue Type: Task > Components: Isis Client Kroviz >Affects Versions: 2.0.0-M5 >Reporter: Jörg Rade >Assignee: Jörg Rade >Priority: Major > Fix For: 2.0.0-RC1 > > > * Parented Lists > * Where In The World > * Icons -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ISIS-3111) Pretty rendering for ChangesDto
[ https://issues.apache.org/jira/browse/ISIS-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood reassigned ISIS-3111: - Assignee: Andi Huber (was: Andi Huber) > Pretty rendering for ChangesDto > --- > > Key: ISIS-3111 > URL: https://issues.apache.org/jira/browse/ISIS-3111 > Project: Isis > Issue Type: Bug > Components: Isis Examples Demo App >Reporter: Daniel Keir Haywood >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M8 > > Attachments: image-2022-08-04-11-57-57-001.png, > image-2022-08-04-11-58-16-650.png, image-2022-08-04-12-28-16-206.png, > image-2022-08-04-15-27-09-553.png, image-2022-08-04-15-27-48-182.png, > image-2022-08-04-15-28-04-365.png, image-2022-08-04-16-18-33-740.png > > > changes (at bottom) just show as toString > [https://demo-wicket.jdo.isis.incode.work/wicket/entity/demo.DomainObjectEntityChangePublishingEnabledEntity:1] > !image-2022-08-04-12-28-16-206.png|width=893,height=91! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-2844) With Secman, SudoService behaves differently from impersonation - should be consistent.
[ https://issues.apache.org/jira/browse/ISIS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2844: -- Attachment: image-2022-08-20-11-20-02-704.png Description: _*Analysis:*_ when sudo service runs and secman is configured, the effective permissions are obtained from the ApplicationUser object, and whichever ApplicationRoles that ApplicationUser happens to have. in contrast, when impersonating then the permissions are obtained from the UserMemento + associated RoleMementos. For consistency, I think that possibly sudo service should also use the UserMemento to obtain the roles in effect. (Note: if not running under sudo service and not impersonating, then we also use the roles from usermemento; but these would have been copied from the ApplicatoinUser on login). In terms of change to the user experience, because a `UserMemento` is immutable and is only populated on login from the `ApplicationUser`, and that it contains the roles, then the user will need to logout and login if they are added to any new roles while logged in. I think this is acceptable. On the other hand... we do need to understand all of the code paths that are affected here. There are 4 callers to `ApplicationUser#getPermissionSet()`: !image-2022-08-20-11-20-02-704.png! ~~~ _*Implementation:*_ In terms of code, it's pretty trivial I think; we just remove the check for userService.isImpersonating() below and always run the first branch, ie query `byUserMemento(...)`. The `byUser(...)` method is probably therefore redundant and could be removed. See code snippet below. !image-2021-08-18-16-24-04-978.png|width=879,height=376! was: _*Analysis:*_ when sudo service runs and secman is configured, the effective permissions are obtained from the ApplicationUser object, and whichever ApplicationRoles that ApplicationUser happens to have. in contrast, when impersonating then the permissions are obtained from the UserMemento + associated RoleMementos. For consistency, I think that sudo service should also use the UserMemento to obtain the roles in effect. (Note: if not running under sudo service and not impersonating, then we also use the roles from usermemento; but these would have been copied from the ApplicatoinUser on login). In terms of change to the user experience, because a `UserMemento` is immutable and is only populated on login from the `ApplicationUser`, and that it contains the roles, then the user will need to logout and login if they are added to any new roles while logged in. I think this is acceptable. ~~~ _*Implementation:*_ In terms of code, it's pretty trivial I think; we just remove the check for userService.isImpersonating() below and always run the first branch, ie query `byUserMemento(...)`. The `byUser(...)` method is probably therefore redundant and could be removed. See code snippet below. !image-2021-08-18-16-24-04-978.png|width=879,height=376! > With Secman, SudoService behaves differently from impersonation - should be > consistent. > --- > > Key: ISIS-2844 > URL: https://issues.apache.org/jira/browse/ISIS-2844 > Project: Isis > Issue Type: Improvement > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M6 >Reporter: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-RC1 > > Attachments: image-2021-08-18-16-24-04-978.png, > image-2022-08-20-11-20-02-704.png > > > _*Analysis:*_ > when sudo service runs and secman is configured, the effective permissions > are obtained from the ApplicationUser object, and whichever ApplicationRoles > that ApplicationUser happens to have. > in contrast, when impersonating then the permissions are obtained from the > UserMemento + associated RoleMementos. > For consistency, I think that possibly sudo service should also use the > UserMemento to obtain the roles in effect. > (Note: if not running under sudo service and not impersonating, then we also > use the roles from usermemento; but these would have been copied from the > ApplicatoinUser on login). > In terms of change to the user experience, because a `UserMemento` is > immutable and is only populated on login from the `ApplicationUser`, and that > it contains the roles, then the user will need to logout and login if they > are added to any new roles while logged in. I think this is acceptable. > > On the other hand... we do need to understand all of the code paths that are > affected here. There are 4 callers to `ApplicationUser#getPermissionSet()`: > !image-2022-08-20-11-20-02-704.png! > ~~~ > _*Implementation:*_ > In terms of code, it's pretty trivial I think; we just remove the check for > userService.isImpersonating() below and always ru
[jira] [Updated] (ISIS-2844) With Secman, SudoService behaves differently from impersonation - should be consistent.
[ https://issues.apache.org/jira/browse/ISIS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2844: -- Description: _*Analysis:*_ when sudo service runs and secman is configured, the effective permissions are obtained from the ApplicationUser object, and whichever ApplicationRoles that ApplicationUser happens to have. in contrast, when impersonating then the permissions are obtained from the UserMemento + associated RoleMementos. For consistency, I think that possibly sudo service should also use the UserMemento to obtain the roles in effect though see additional analysis below, I'm not 100% sure on this. (Note: if not running under sudo service and not impersonating, then we also use the roles from usermemento; but these would have been copied from the ApplicatoinUser on login). In terms of change to the user experience, because a `UserMemento` is immutable and is only populated on login from the `ApplicationUser`, and that it contains the roles, then the user will need to logout and login if they are added to any new roles while logged in. I think this is acceptable. On the other hand... we do need to understand all of the code paths that are affected here. There are 4 callers to `ApplicationUser#getPermissionSet()`: !image-2022-08-20-11-20-02-704.png|width=601,height=177! This issue was raised originally in the context of `AuthorizorSecman#grants` to determine the effective permissoin, where it looks up the current `ApplicatoinUser` but the `ApplicationUser` (as currently implemented) is aware that impersonation can happen and if so to use the `UserMemento` rather than itself. But what of the other 3 callers? So it might be that the knowledge about impersonatoin should reside in the callers, eg in `AuthorizorSecman#grants` rather than in `ApplicationUser#getPermissionSet()`. So, more analysis needed, I think. ~~~ _*Implementation (if decide to go ahead):*_ In terms of code, it's pretty trivial I think; we just remove the check for userService.isImpersonating() below and always run the first branch, ie query `byUserMemento(...)`. The `byUser(...)` method is probably therefore redundant and could be removed. See code snippet below. !image-2021-08-18-16-24-04-978.png|width=879,height=376! was: _*Analysis:*_ when sudo service runs and secman is configured, the effective permissions are obtained from the ApplicationUser object, and whichever ApplicationRoles that ApplicationUser happens to have. in contrast, when impersonating then the permissions are obtained from the UserMemento + associated RoleMementos. For consistency, I think that possibly sudo service should also use the UserMemento to obtain the roles in effect. (Note: if not running under sudo service and not impersonating, then we also use the roles from usermemento; but these would have been copied from the ApplicatoinUser on login). In terms of change to the user experience, because a `UserMemento` is immutable and is only populated on login from the `ApplicationUser`, and that it contains the roles, then the user will need to logout and login if they are added to any new roles while logged in. I think this is acceptable. On the other hand... we do need to understand all of the code paths that are affected here. There are 4 callers to `ApplicationUser#getPermissionSet()`: !image-2022-08-20-11-20-02-704.png! ~~~ _*Implementation:*_ In terms of code, it's pretty trivial I think; we just remove the check for userService.isImpersonating() below and always run the first branch, ie query `byUserMemento(...)`. The `byUser(...)` method is probably therefore redundant and could be removed. See code snippet below. !image-2021-08-18-16-24-04-978.png|width=879,height=376! > With Secman, SudoService behaves differently from impersonation - should be > consistent. > --- > > Key: ISIS-2844 > URL: https://issues.apache.org/jira/browse/ISIS-2844 > Project: Isis > Issue Type: Improvement > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M6 >Reporter: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-RC1 > > Attachments: image-2021-08-18-16-24-04-978.png, > image-2022-08-20-11-20-02-704.png > > > _*Analysis:*_ > when sudo service runs and secman is configured, the effective permissions > are obtained from the ApplicationUser object, and whichever ApplicationRoles > that ApplicationUser happens to have. > in contrast, when impersonating then the permissions are obtained from the > UserMemento + associated RoleMementos. > For consistency, I think that possibly sudo service should also use the > UserMemento to obtain the roles in effect though see additional
[jira] [Updated] (ISIS-2844) With Secman, SudoService behaves differently from impersonation - should be consistent in appropriate contexts...
[ https://issues.apache.org/jira/browse/ISIS-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2844: -- Summary: With Secman, SudoService behaves differently from impersonation - should be consistent in appropriate contexts... (was: With Secman, SudoService behaves differently from impersonation - should be consistent.) > With Secman, SudoService behaves differently from impersonation - should be > consistent in appropriate contexts... > - > > Key: ISIS-2844 > URL: https://issues.apache.org/jira/browse/ISIS-2844 > Project: Isis > Issue Type: Improvement > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M6 >Reporter: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-RC1 > > Attachments: image-2021-08-18-16-24-04-978.png, > image-2022-08-20-11-20-02-704.png > > > _*Analysis:*_ > when sudo service runs and secman is configured, the effective permissions > are obtained from the ApplicationUser object, and whichever ApplicationRoles > that ApplicationUser happens to have. > in contrast, when impersonating then the permissions are obtained from the > UserMemento + associated RoleMementos. > For consistency, I think that possibly sudo service should also use the > UserMemento to obtain the roles in effect though see additional analysis > below, I'm not 100% sure on this. > (Note: if not running under sudo service and not impersonating, then we also > use the roles from usermemento; but these would have been copied from the > ApplicatoinUser on login). > In terms of change to the user experience, because a `UserMemento` is > immutable and is only populated on login from the `ApplicationUser`, and that > it contains the roles, then the user will need to logout and login if they > are added to any new roles while logged in. I think this is acceptable. > > On the other hand... we do need to understand all of the code paths that are > affected here. There are 4 callers to `ApplicationUser#getPermissionSet()`: > !image-2022-08-20-11-20-02-704.png|width=601,height=177! > This issue was raised originally in the context of `AuthorizorSecman#grants` > to determine the effective permissoin, where it looks up the current > `ApplicatoinUser` but the `ApplicationUser` (as currently implemented) is > aware that impersonation can happen and if so to use the `UserMemento` rather > than itself. But what of the other 3 callers? So it might be that the > knowledge about impersonatoin should reside in the callers, eg in > `AuthorizorSecman#grants` rather than in > `ApplicationUser#getPermissionSet()`. > So, more analysis needed, I think. > ~~~ > _*Implementation (if decide to go ahead):*_ > In terms of code, it's pretty trivial I think; we just remove the check for > userService.isImpersonating() below and always run the first branch, ie query > `byUserMemento(...)`. The `byUser(...)` method is probably therefore > redundant and could be removed. See code snippet below. > !image-2021-08-18-16-24-04-978.png|width=879,height=376! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ISIS-2858) AbstractUserAndRoleScript and similar should inject into suppliers.
[ https://issues.apache.org/jira/browse/ISIS-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood resolved ISIS-2858. --- Resolution: Fixed > AbstractUserAndRoleScript and similar should inject into suppliers. > --- > > Key: ISIS-2858 > URL: https://issues.apache.org/jira/browse/ISIS-2858 > Project: Isis > Issue Type: Improvement > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M6 >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-M8 > > > Or alternatively, rather than pass into the constructor, could provide hook > methods to return the values? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ISIS-2959) [Wicket Viewer] menu bar lists which are too long (eg Prototyping) should have a scroll bar.
[ https://issues.apache.org/jira/browse/ISIS-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood reassigned ISIS-2959: - Assignee: Daniel Keir Haywood (was: Andi Huber) > [Wicket Viewer] menu bar lists which are too long (eg Prototyping) should > have a scroll bar. > > > Key: ISIS-2959 > URL: https://issues.apache.org/jira/browse/ISIS-2959 > Project: Isis > Issue Type: Improvement > Components: Wicket Viewer >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ISIS-2959) [Wicket Viewer] menu bar lists which are too long (eg Prototyping) should have a scroll bar.
[ https://issues.apache.org/jira/browse/ISIS-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood resolved ISIS-2959. --- Resolution: Fixed > [Wicket Viewer] menu bar lists which are too long (eg Prototyping) should > have a scroll bar. > > > Key: ISIS-2959 > URL: https://issues.apache.org/jira/browse/ISIS-2959 > Project: Isis > Issue Type: Improvement > Components: Wicket Viewer >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-2959) [Wicket Viewer] menu bar lists which are too long (eg Prototyping) should have a scroll bar.
[ https://issues.apache.org/jira/browse/ISIS-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-2959: -- Fix Version/s: 2.0.0-M8 (was: 2.0.0-RC1) > [Wicket Viewer] menu bar lists which are too long (eg Prototyping) should > have a scroll bar. > > > Key: ISIS-2959 > URL: https://issues.apache.org/jira/browse/ISIS-2959 > Project: Isis > Issue Type: Improvement > Components: Wicket Viewer >Reporter: Daniel Keir Haywood >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3137) Rename JIRA project
Daniel Keir Haywood created ISIS-3137: - Summary: Rename JIRA project Key: ISIS-3137 URL: https://issues.apache.org/jira/browse/ISIS-3137 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3136) Rename mailing lists
Daniel Keir Haywood created ISIS-3136: - Summary: Rename mailing lists Key: ISIS-3136 URL: https://issues.apache.org/jira/browse/ISIS-3136 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3139) Rename non-ASF github apache-isis-committers/isis-nightly repo
Daniel Keir Haywood created ISIS-3139: - Summary: Rename non-ASF github apache-isis-committers/isis-nightly repo Key: ISIS-3139 URL: https://issues.apache.org/jira/browse/ISIS-3139 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3138) Rename ASF git repositories
Daniel Keir Haywood created ISIS-3138: - Summary: Rename ASF git repositories Key: ISIS-3138 URL: https://issues.apache.org/jira/browse/ISIS-3138 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3139) Create non-ASF github apache-isis-committers/isis-nightly repo
[ https://issues.apache.org/jira/browse/ISIS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3139: -- Description: adapt from current github apache-isis-committers/isis-nightly repo > Create non-ASF github apache-isis-committers/isis-nightly repo > -- > > Key: ISIS-3139 > URL: https://issues.apache.org/jira/browse/ISIS-3139 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Priority: Major > > adapt from current github apache-isis-committers/isis-nightly repo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3140) Create non-ASF "apachecauseway" namespace on docker hub (equiv to "apacheisis")
Daniel Keir Haywood created ISIS-3140: - Summary: Create non-ASF "apachecauseway" namespace on docker hub (equiv to "apacheisis") Key: ISIS-3140 URL: https://issues.apache.org/jira/browse/ISIS-3140 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3139) Create non-ASF github apache-causeway-committers/causeway-nightly repo
[ https://issues.apache.org/jira/browse/ISIS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3139: -- Summary: Create non-ASF github apache-causeway-committers/causeway-nightly repo (was: Create non-ASF github apache-isis-committers/isis-nightly repo) > Create non-ASF github apache-causeway-committers/causeway-nightly repo > -- > > Key: ISIS-3139 > URL: https://issues.apache.org/jira/browse/ISIS-3139 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Priority: Major > > adapt from current github apache-isis-committers/isis-nightly repo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3139) Create non-ASF github apache-isis-committers/isis-nightly repo
[ https://issues.apache.org/jira/browse/ISIS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3139: -- Summary: Create non-ASF github apache-isis-committers/isis-nightly repo (was: Rename non-ASF github apache-isis-committers/isis-nightly repo) > Create non-ASF github apache-isis-committers/isis-nightly repo > -- > > Key: ISIS-3139 > URL: https://issues.apache.org/jira/browse/ISIS-3139 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3138) Rename ASF git repositories
[ https://issues.apache.org/jira/browse/ISIS-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3138: -- Description: [https://github.com/search?q=isis+user%3Aapache&type=Repositories&ref=advsearch&l=&l=] Raise an infra ticket to rename these: * apache/isis * apache/isis-site * apache/isis-antora (Antora theme as used by isis-site) * apache/isis-app-helloworld * apache/isis-app-simpleapp * apache/isis-app-demo (petclinic demo app) raise an infra ticket to remove these (currently unused and empty) * apache/isis-app-todoapp * apache/isis-app-kitchensink * apache/isis-app-neoapp > Rename ASF git repositories > --- > > Key: ISIS-3138 > URL: https://issues.apache.org/jira/browse/ISIS-3138 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-rename > > > [https://github.com/search?q=isis+user%3Aapache&type=Repositories&ref=advsearch&l=&l=] > > Raise an infra ticket to rename these: > * apache/isis > * apache/isis-site > * apache/isis-antora (Antora theme as used by isis-site) > * apache/isis-app-helloworld > * apache/isis-app-simpleapp > * apache/isis-app-demo (petclinic demo app) > raise an infra ticket to remove these (currently unused and empty) > * apache/isis-app-todoapp > * apache/isis-app-kitchensink > * apache/isis-app-neoapp > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3141) Redirect isis.apache.org to causeway.apache.org
Daniel Keir Haywood created ISIS-3141: - Summary: Redirect isis.apache.org to causeway.apache.org Key: ISIS-3141 URL: https://issues.apache.org/jira/browse/ISIS-3141 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3142) Apply name change to code and docs (using Rename.groovy script)
Daniel Keir Haywood created ISIS-3142: - Summary: Apply name change to code and docs (using Rename.groovy script) Key: ISIS-3142 URL: https://issues.apache.org/jira/browse/ISIS-3142 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3143) Update .ppt and other binary docs with name change.
Daniel Keir Haywood created ISIS-3143: - Summary: Update .ppt and other binary docs with name change. Key: ISIS-3143 URL: https://issues.apache.org/jira/browse/ISIS-3143 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3143) Update .pptx and other binary docs with name change.
[ https://issues.apache.org/jira/browse/ISIS-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3143: -- Summary: Update .pptx and other binary docs with name change. (was: Update .ppt and other binary docs with name change.) > Update .pptx and other binary docs with name change. > > > Key: ISIS-3143 > URL: https://issues.apache.org/jira/browse/ISIS-3143 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-rename > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3144) Adapt apache-isis-committers/isis-nightly to keep publishing isis nightly builds.
Daniel Keir Haywood created ISIS-3144: - Summary: Adapt apache-isis-committers/isis-nightly to keep publishing isis nightly builds. Key: ISIS-3144 URL: https://issues.apache.org/jira/browse/ISIS-3144 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3144) Adapt apache-isis-committers/isis-nightly to keep publishing isis nightly builds.
[ https://issues.apache.org/jira/browse/ISIS-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3144: -- Description: As an ASF project, we won't be publishing isis jars once we've cut over. But we would like to informally continue to publish isis jars with the old names as nightly builds. This will allow folk to switch over to "causeway" at their leisure. So, once we have renamed apache/isis -> apache/causeway and updated the code/docs to use "causeway" rather than "isis", we then update its script so that: a) checks out from apache/causeway rather than apache/isis b) as an additional step, uses Rename.groovy to dynamically rename everything from "causeway" back to "isis" c) continues as before. > Adapt apache-isis-committers/isis-nightly to keep publishing isis nightly > builds. > - > > Key: ISIS-3144 > URL: https://issues.apache.org/jira/browse/ISIS-3144 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-rename > > > As an ASF project, we won't be publishing isis jars once we've cut over. But > we would like to informally continue to publish isis jars with the old names > as nightly builds. This will allow folk to switch over to "causeway" at > their leisure. > So, once we have renamed apache/isis -> apache/causeway and updated the > code/docs to use "causeway" rather than "isis", we then update its script so > that: > a) checks out from apache/causeway rather than apache/isis > b) as an additional step, uses Rename.groovy to dynamically rename everything > from "causeway" back to "isis" > c) continues as before. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3145) Issue press release about name change.
[ https://issues.apache.org/jira/browse/ISIS-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3145: -- Description: for reference, see https://issues.apache.org/jira/browse/POLYGENE-203 > Issue press release about name change. > -- > > Key: ISIS-3145 > URL: https://issues.apache.org/jira/browse/ISIS-3145 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-rename > > > for reference, see https://issues.apache.org/jira/browse/POLYGENE-203 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3145) Issue press release about name change.
Daniel Keir Haywood created ISIS-3145: - Summary: Issue press release about name change. Key: ISIS-3145 URL: https://issues.apache.org/jira/browse/ISIS-3145 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3145) Issue press release about name change.
[ https://issues.apache.org/jira/browse/ISIS-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3145: -- Description: would prefer this is done towards the end of the process. for reference, see https://issues.apache.org/jira/browse/POLYGENE-203 was:for reference, see https://issues.apache.org/jira/browse/POLYGENE-203 > Issue press release about name change. > -- > > Key: ISIS-3145 > URL: https://issues.apache.org/jira/browse/ISIS-3145 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-rename > > > would prefer this is done towards the end of the process. > > for reference, see https://issues.apache.org/jira/browse/POLYGENE-203 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3147) Update docs with new logo
Daniel Keir Haywood created ISIS-3147: - Summary: Update docs with new logo Key: ISIS-3147 URL: https://issues.apache.org/jira/browse/ISIS-3147 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3146) Vote for new Logo
Daniel Keir Haywood created ISIS-3146: - Summary: Vote for new Logo Key: ISIS-3146 URL: https://issues.apache.org/jira/browse/ISIS-3146 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3148) Apply name change to project doap file and in the STATUS file.
Daniel Keir Haywood created ISIS-3148: - Summary: Apply name change to project doap file and in the STATUS file. Key: ISIS-3148 URL: https://issues.apache.org/jira/browse/ISIS-3148 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename Probably the Rename.groovy script will take care of this, but we might want to revert some changes so that we can preserve "isis" as the name used for releases until now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3149) Apply/confirm name change to apache.org navigation
Daniel Keir Haywood created ISIS-3149: - Summary: Apply/confirm name change to apache.org navigation Key: ISIS-3149 URL: https://issues.apache.org/jira/browse/ISIS-3149 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3149) Apply/confirm name change to apache.org navigation
[ https://issues.apache.org/jira/browse/ISIS-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3149: -- Description: cf https://issues.apache.org/jira/browse/POLYGENE-211 > Apply/confirm name change to apache.org navigation > -- > > Key: ISIS-3149 > URL: https://issues.apache.org/jira/browse/ISIS-3149 > Project: Isis > Issue Type: Sub-task >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-rename > > > cf https://issues.apache.org/jira/browse/POLYGENE-211 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3150) Sonarcloud.io
Daniel Keir Haywood created ISIS-3150: - Summary: Sonarcloud.io Key: ISIS-3150 URL: https://issues.apache.org/jira/browse/ISIS-3150 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3151) Fisheye
Daniel Keir Haywood created ISIS-3151: - Summary: Fisheye Key: ISIS-3151 URL: https://issues.apache.org/jira/browse/ISIS-3151 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3152) Deploy config + DNS for simpleapp, helloworld, demoapp
Daniel Keir Haywood created ISIS-3152: - Summary: Deploy config + DNS for simpleapp, helloworld, demoapp Key: ISIS-3152 URL: https://issues.apache.org/jira/browse/ISIS-3152 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3153) Update contents of antora template (in apache/isis-antora repo) and rebuild website
Daniel Keir Haywood created ISIS-3153: - Summary: Update contents of antora template (in apache/isis-antora repo) and rebuild website Key: ISIS-3153 URL: https://issues.apache.org/jira/browse/ISIS-3153 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3154) Request INFRA to enable publishing of new groupId to repository.apache.org
Daniel Keir Haywood created ISIS-3154: - Summary: Request INFRA to enable publishing of new groupId to repository.apache.org Key: ISIS-3154 URL: https://issues.apache.org/jira/browse/ISIS-3154 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename cf https://issues.apache.org/jira/browse/POLYGENE-212 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3155) Apply name change to dist.apache.org
Daniel Keir Haywood created ISIS-3155: - Summary: Apply name change to dist.apache.org Key: ISIS-3155 URL: https://issues.apache.org/jira/browse/ISIS-3155 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename cf https://issues.apache.org/jira/browse/POLYGENE-213 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3156) Change name in Board Report Schedule
Daniel Keir Haywood created ISIS-3156: - Summary: Change name in Board Report Schedule Key: ISIS-3156 URL: https://issues.apache.org/jira/browse/ISIS-3156 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename cf https://issues.apache.org/jira/browse/POLYGENE-216 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3158) Change affiliations.txt
Daniel Keir Haywood created ISIS-3158: - Summary: Change affiliations.txt Key: ISIS-3158 URL: https://issues.apache.org/jira/browse/ISIS-3158 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename cf https://issues.apache.org/jira/browse/POLYGENE-218 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3157) Change in irs-disclosures.txt
Daniel Keir Haywood created ISIS-3157: - Summary: Change in irs-disclosures.txt Key: ISIS-3157 URL: https://issues.apache.org/jira/browse/ISIS-3157 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename cf https://issues.apache.org/jira/browse/POLYGENE-217 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3159) Update committers/board/committee-info.txt
Daniel Keir Haywood created ISIS-3159: - Summary: Update committers/board/committee-info.txt Key: ISIS-3159 URL: https://issues.apache.org/jira/browse/ISIS-3159 Project: Isis Issue Type: Sub-task Reporter: Daniel Keir Haywood Fix For: 2.0.0-rename cf https://issues.apache.org/jira/browse/POLYGENE-219 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3160) remove IsisConfigurationLegacy ?
Daniel Keir Haywood created ISIS-3160: - Summary: remove IsisConfigurationLegacy ? Key: ISIS-3160 URL: https://issues.apache.org/jira/browse/ISIS-3160 Project: Isis Issue Type: Improvement Reporter: Daniel Keir Haywood Fix For: 2.0.0-RC1 seems like this class is no longer used anywhere? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3161) confirm usage of spring-instrument-5.3.5.jar for JPA weaving (or otherwise...?)
Daniel Keir Haywood created ISIS-3161: - Summary: confirm usage of spring-instrument-5.3.5.jar for JPA weaving (or otherwise...?) Key: ISIS-3161 URL: https://issues.apache.org/jira/browse/ISIS-3161 Project: Isis Issue Type: Improvement Reporter: Daniel Keir Haywood Fix For: 2.0.0-RC1 we have docs that reference this JAR; are they correct? or perhaps it should be eclipselink.jar, as per [https://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Advanced_JPA_Development/Performance/Weaving/Dynamic_Weaving] ? but then [https://stackoverflow.com/a/24958577] suggests spring-instrument.jar, so ...? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (ISIS-3125) [Regression] nested Class Wicket in Isis Configuration is not Serializable
[ https://issues.apache.org/jira/browse/ISIS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood reopened ISIS-3125: --- > [Regression] nested Class Wicket in Isis Configuration is not Serializable > -- > > Key: ISIS-3125 > URL: https://issues.apache.org/jira/browse/ISIS-3125 > Project: Isis > Issue Type: Improvement > Components: Isis Viewer Wicket >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Blocker > Fix For: 2.0.0-M8 > > > Need to revert removal of WicketViewerSettings class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ISIS-3125) [Regression] nested Class Wicket in Isis Configuration is not Serializable
[ https://issues.apache.org/jira/browse/ISIS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood closed ISIS-3125. - Resolution: Fixed > [Regression] nested Class Wicket in Isis Configuration is not Serializable > -- > > Key: ISIS-3125 > URL: https://issues.apache.org/jira/browse/ISIS-3125 > Project: Isis > Issue Type: Improvement > Components: Isis Viewer Wicket >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Blocker > Fix For: 2.0.0-M8 > > > Need to revert removal of WicketViewerSettings class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3162) Download "object layouts zip" throws exception
Daniel Keir Haywood created ISIS-3162: - Summary: Download "object layouts zip" throws exception Key: ISIS-3162 URL: https://issues.apache.org/jira/browse/ISIS-3162 Project: Isis Issue Type: Bug Affects Versions: 2.0.0-M8 Reporter: Daniel Keir Haywood Fix For: 2.0.0-RC1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3163) secman UserManager shows "metadata" as rather ugly region
Daniel Keir Haywood created ISIS-3163: - Summary: secman UserManager shows "metadata" as rather ugly region Key: ISIS-3163 URL: https://issues.apache.org/jira/browse/ISIS-3163 Project: Isis Issue Type: Bug Affects Versions: 2.0.0-M8 Reporter: Daniel Keir Haywood Fix For: 2.0.0-RC1 Attachments: image-2022-08-22-14-08-51-462.png !image-2022-08-22-14-08-51-462.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3163) secman UserManager shows "metadata" as rather ugly region
[ https://issues.apache.org/jira/browse/ISIS-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3163: -- Description: !image-2022-08-22-14-08-51-462.png|width=1453,height=281! (was: !image-2022-08-22-14-08-51-462.png!) > secman UserManager shows "metadata" as rather ugly region > - > > Key: ISIS-3163 > URL: https://issues.apache.org/jira/browse/ISIS-3163 > Project: Isis > Issue Type: Bug >Affects Versions: 2.0.0-M8 >Reporter: Daniel Keir Haywood >Priority: Trivial > Fix For: 2.0.0-RC1 > > Attachments: image-2022-08-22-14-08-51-462.png > > > !image-2022-08-22-14-08-51-462.png|width=1453,height=281! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3163) secman UserManager shows "metadata" as rather ugly region
[ https://issues.apache.org/jira/browse/ISIS-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3163: -- Description: !image-2022-08-22-14-10-09-640.png|width=614,height=341! was:!image-2022-08-22-14-08-51-462.png|width=1453,height=281! > secman UserManager shows "metadata" as rather ugly region > - > > Key: ISIS-3163 > URL: https://issues.apache.org/jira/browse/ISIS-3163 > Project: Isis > Issue Type: Bug >Affects Versions: 2.0.0-M8 >Reporter: Daniel Keir Haywood >Priority: Trivial > Fix For: 2.0.0-RC1 > > Attachments: image-2022-08-22-14-08-51-462.png, > image-2022-08-22-14-10-09-640.png, image-2022-08-22-14-10-43-847.png > > > !image-2022-08-22-14-10-09-640.png|width=614,height=341! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3163) secman UserManager shows "metadata" as rather ugly region
[ https://issues.apache.org/jira/browse/ISIS-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3163: -- Description: !image-2022-08-22-14-10-09-640.png|width=614,height=341! !image-2022-08-22-14-10-43-847.png|width=633,height=613! was: !image-2022-08-22-14-10-09-640.png|width=614,height=341! > secman UserManager shows "metadata" as rather ugly region > - > > Key: ISIS-3163 > URL: https://issues.apache.org/jira/browse/ISIS-3163 > Project: Isis > Issue Type: Bug >Affects Versions: 2.0.0-M8 >Reporter: Daniel Keir Haywood >Priority: Trivial > Fix For: 2.0.0-RC1 > > Attachments: image-2022-08-22-14-08-51-462.png, > image-2022-08-22-14-10-09-640.png, image-2022-08-22-14-10-43-847.png > > > !image-2022-08-22-14-10-09-640.png|width=614,height=341! > !image-2022-08-22-14-10-43-847.png|width=633,height=613! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3163) secman UserManager shows "metadata" as rather ugly region
[ https://issues.apache.org/jira/browse/ISIS-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3163: -- Attachment: image-2022-08-22-14-10-09-640.png > secman UserManager shows "metadata" as rather ugly region > - > > Key: ISIS-3163 > URL: https://issues.apache.org/jira/browse/ISIS-3163 > Project: Isis > Issue Type: Bug >Affects Versions: 2.0.0-M8 >Reporter: Daniel Keir Haywood >Priority: Trivial > Fix For: 2.0.0-RC1 > > Attachments: image-2022-08-22-14-08-51-462.png, > image-2022-08-22-14-10-09-640.png, image-2022-08-22-14-10-43-847.png > > > !image-2022-08-22-14-08-51-462.png|width=1453,height=281! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3163) secman UserManager shows "metadata" as rather ugly region
[ https://issues.apache.org/jira/browse/ISIS-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3163: -- Attachment: image-2022-08-22-14-10-43-847.png > secman UserManager shows "metadata" as rather ugly region > - > > Key: ISIS-3163 > URL: https://issues.apache.org/jira/browse/ISIS-3163 > Project: Isis > Issue Type: Bug >Affects Versions: 2.0.0-M8 >Reporter: Daniel Keir Haywood >Priority: Trivial > Fix For: 2.0.0-RC1 > > Attachments: image-2022-08-22-14-08-51-462.png, > image-2022-08-22-14-10-09-640.png, image-2022-08-22-14-10-43-847.png > > > !image-2022-08-22-14-10-09-640.png|width=614,height=341! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3163) secman UserManager and RoleManager both show "metadata" as rather ugly region at end; let's move top right; also ensure contributed actions are available through it.
[ https://issues.apache.org/jira/browse/ISIS-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3163: -- Summary: secman UserManager and RoleManager both show "metadata" as rather ugly region at end; let's move top right; also ensure contributed actions are available through it. (was: secman UserManager shows "metadata" as rather ugly region) > secman UserManager and RoleManager both show "metadata" as rather ugly region > at end; let's move top right; also ensure contributed actions are available > through it. > - > > Key: ISIS-3163 > URL: https://issues.apache.org/jira/browse/ISIS-3163 > Project: Isis > Issue Type: Bug >Affects Versions: 2.0.0-M8 >Reporter: Daniel Keir Haywood >Priority: Trivial > Fix For: 2.0.0-RC1 > > Attachments: image-2022-08-22-14-08-51-462.png, > image-2022-08-22-14-10-09-640.png, image-2022-08-22-14-10-43-847.png > > > !image-2022-08-22-14-10-09-640.png|width=614,height=341! > !image-2022-08-22-14-10-43-847.png|width=633,height=613! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3164) secman ApplicationUser view shows only icon, no columns, of each associated role in table
Daniel Keir Haywood created ISIS-3164: - Summary: secman ApplicationUser view shows only icon, no columns, of each associated role in table Key: ISIS-3164 URL: https://issues.apache.org/jira/browse/ISIS-3164 Project: Isis Issue Type: Bug Components: Isis Extensions SecMan Affects Versions: 2.0.0-M8 Reporter: Daniel Keir Haywood Fix For: 2.0.0-RC1 Attachments: image-2022-08-22-14-13-46-602.png !image-2022-08-22-14-13-46-602.png|width=1564,height=439! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ISIS-3117) Add missing sha256 or sha512 to already released isis/isis-parent/isis-parent-2.0.0-M7-source-release.zip
[ https://issues.apache.org/jira/browse/ISIS-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583408#comment-17583408 ] Daniel Keir Haywood commented on ISIS-3117: --- Have fixed for M7, amended instructions going forward. the sha512's are created, but needs to be explicitly svn add'd to dist.apache.org/isis-dist. > Add missing sha256 or sha512 to already released > isis/isis-parent/isis-parent-2.0.0-M7-source-release.zip > - > > Key: ISIS-3117 > URL: https://issues.apache.org/jira/browse/ISIS-3117 > Project: Isis > Issue Type: Task > Components: Isis CI & Build Scripts >Affects Versions: 2.0.0-M7 >Reporter: Andi Huber >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ISIS-2858) AbstractUserAndRoleScript and similar should inject into suppliers.
[ https://issues.apache.org/jira/browse/ISIS-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood closed ISIS-2858. - > AbstractUserAndRoleScript and similar should inject into suppliers. > --- > > Key: ISIS-2858 > URL: https://issues.apache.org/jira/browse/ISIS-2858 > Project: Isis > Issue Type: Improvement > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M6 >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-M8 > > > Or alternatively, rather than pass into the constructor, could provide hook > methods to return the values? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ISIS-2959) [Wicket Viewer] menu bar lists which are too long (eg Prototyping) should have a scroll bar.
[ https://issues.apache.org/jira/browse/ISIS-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood closed ISIS-2959. - > [Wicket Viewer] menu bar lists which are too long (eg Prototyping) should > have a scroll bar. > > > Key: ISIS-2959 > URL: https://issues.apache.org/jira/browse/ISIS-2959 > Project: Isis > Issue Type: Improvement > Components: Wicket Viewer >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (ISIS-3117) Add missing sha256 or sha512 to already released isis/isis-parent/isis-parent-2.0.0-M7-source-release.zip
[ https://issues.apache.org/jira/browse/ISIS-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood closed ISIS-3117. - Resolution: Fixed > Add missing sha256 or sha512 to already released > isis/isis-parent/isis-parent-2.0.0-M7-source-release.zip > - > > Key: ISIS-3117 > URL: https://issues.apache.org/jira/browse/ISIS-3117 > Project: Isis > Issue Type: Task > Components: Isis CI & Build Scripts >Affects Versions: 2.0.0-M7 >Reporter: Andi Huber >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3168) Remove Wicket viewer registration stuff; better to do this externally with keycloak etc.
Daniel Keir Haywood created ISIS-3168: - Summary: Remove Wicket viewer registration stuff; better to do this externally with keycloak etc. Key: ISIS-3168 URL: https://issues.apache.org/jira/browse/ISIS-3168 Project: Isis Issue Type: Improvement Reporter: Daniel Keir Haywood Fix For: 2.0.0-RC1 trimming unnecessary features. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ISIS-3169) Autocreate delegated applicationusers if using Spring Oauth2/Keycloak
Daniel Keir Haywood created ISIS-3169: - Summary: Autocreate delegated applicationusers if using Spring Oauth2/Keycloak Key: ISIS-3169 URL: https://issues.apache.org/jira/browse/ISIS-3169 Project: Isis Issue Type: New Feature Components: Isis Extensions SecMan Affects Versions: 2.0.0-M7 Reporter: Daniel Keir Haywood Assignee: Daniel Keir Haywood Fix For: 2.0.0-M8 Also make keycloak more robust in its handling of extracting roles out of the token. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ISIS-3169) Autocreate delegated applicationusers if using Spring Oauth2/Keycloak
[ https://issues.apache.org/jira/browse/ISIS-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood resolved ISIS-3169. --- Resolution: Fixed > Autocreate delegated applicationusers if using Spring Oauth2/Keycloak > - > > Key: ISIS-3169 > URL: https://issues.apache.org/jira/browse/ISIS-3169 > Project: Isis > Issue Type: New Feature > Components: Isis Extensions SecMan >Affects Versions: 2.0.0-M7 >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Minor > Fix For: 2.0.0-M8 > > > Also make keycloak more robust in its handling of extracting roles out of the > token. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ISIS-3176) Add missing @ObjectSupport methods
[ https://issues.apache.org/jira/browse/ISIS-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood reassigned ISIS-3176: - Assignee: Daniel Keir Haywood > Add missing @ObjectSupport methods > -- > > Key: ISIS-3176 > URL: https://issues.apache.org/jira/browse/ISIS-3176 > Project: Isis > Issue Type: Bug >Reporter: Daniel Keir Haywood >Assignee: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > > so can be used with ENCAPSULATION_ENABLED -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ISIS-3176) Add missing @ObjectSupport methods
[ https://issues.apache.org/jira/browse/ISIS-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Keir Haywood updated ISIS-3176: -- Fix Version/s: 2.0.0-M8 > Add missing @ObjectSupport methods > -- > > Key: ISIS-3176 > URL: https://issues.apache.org/jira/browse/ISIS-3176 > Project: Isis > Issue Type: Bug >Reporter: Daniel Keir Haywood >Priority: Major > Fix For: 2.0.0-M8 > > > so can be used with ENCAPSULATION_ENABLED -- This message was sent by Atlassian Jira (v8.20.10#820010)
