[GitHub] [isis] dependabot[bot] opened a new pull request, #1040: Bump approvaltests from 17.1.0 to 17.2.1

2022-08-02 Thread GitBox


dependabot[bot] opened a new pull request, #1040:
URL: https://github.com/apache/isis/pull/1040

   Bumps [approvaltests](https://github.com/approvals/ApprovalTests.Java) from 
17.1.0 to 17.2.1.
   
   Release notes
   Sourced from https://github.com/approvals/ApprovalTests.Java/releases;>approvaltests's 
releases.
   
   Approvals.NAMES
   ExtraInformation.Approvals.txt
   the old way
   There is now a new way to add information to approval names. Previously 
the way to add additional information was
   try (NamedEnvironment ne1 = 
NamerFactory.asOsSpecificTest()) { 
   try (NamedEnvironment ne2 = NamerFactory.asMachineNameSpecificTest()) { 
   Approvals.verify(hello, World!);
   }
   } 
   
   the new way
   We now added a cleaner and more thread-safe method of passing in an 
Options to the additional information.
   Options options = 
Approvals.NAMES.asOsSpecificTest().and(Approvals.NAMES::asMachineNameSpecificTest);
   Approvals.verify(hello, World!, options);
   
   We're not removing the previous way, we're simply adding the new way. In 
the future, we will update everything underneath to be more thread-safe.
   More
   We're having a new reporter for TortoiseGIT. Thank you https://github.com/pfichtner;>@​pfichtner
   
   
   
   Commits
   
   https://github.com/approvals/ApprovalTests.Java/commit/356c630610f864cbce8739177883b070c7e4b372;>356c630
 e needs to work on windows as well
   https://github.com/approvals/ApprovalTests.Java/commit/da1d58a0f50080453a35d3dbc0b2c54e022416e9;>da1d58a
 e sed for Ubuntu
   https://github.com/approvals/ApprovalTests.Java/commit/c39a9bf861627e236e610b74caebfae2b492f229;>c39a9bf
 e update actions to use scripts
   https://github.com/approvals/ApprovalTests.Java/commit/50630f5a2f2c07941c6a2982fa04ead8bc2f366c;>50630f5
 e compatible with macos
   https://github.com/approvals/ApprovalTests.Java/commit/a39cba5d21570e0d43110adbdf654498ceb81e92;>a39cba5
 e scripts for formatting
   https://github.com/approvals/ApprovalTests.Java/commit/c852ebf03f0db05c00c5f0d0b8083b0342b7c4dd;>c852ebf
 Bump gson from 2.9.0 to 2.9.1
   https://github.com/approvals/ApprovalTests.Java/commit/f27771fcfe0661c5c01e65488cf00bc7bd407c4c;>f27771f
 F!! Options.and(...)
   https://github.com/approvals/ApprovalTests.Java/commit/16c6edcaf6beba2459269662b73df305625260cc;>16c6edc
 a   reformat code
   https://github.com/approvals/ApprovalTests.Java/commit/718d87fa5a4c4a345a306c77c06c662d43b7c09f;>718d87f
 Merge pull request https://github-redirect.dependabot.com/approvals/ApprovalTests.Java/issues/287;>#287
 from pfichtner/tortoise-git
   https://github.com/approvals/ApprovalTests.Java/commit/0add6f43b24f5d48d98fbeb3aec687b80c9ec395;>0add6f4
 Merge pull request https://github-redirect.dependabot.com/approvals/ApprovalTests.Java/issues/284;>#284
 from approvals/dependabot/maven/org.junit.jupiter-jun...
   Additional commits viewable in https://github.com/approvals/ApprovalTests.Java/compare/17.1.0...17.2.1;>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.approvaltests:approvaltests=maven=17.1.0=17.2.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to 

[GitHub] [isis] dependabot[bot] opened a new pull request, #1039: Bump vaadin.version from 23.1.3 to 23.1.4

2022-08-02 Thread GitBox


dependabot[bot] opened a new pull request, #1039:
URL: https://github.com/apache/isis/pull/1039

   Bumps `vaadin.version` from 23.1.3 to 23.1.4.
   Updates `vaadin-bom` from 23.1.3 to 23.1.4
   
   Updates `vaadin-maven-plugin` from 23.1.3 to 23.1.4
   
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@isis.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[jira] [Commented] (ISIS-3002) Bring in extensions/core/outbox-publisher (from incode-platform)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574420#comment-17574420
 ] 

ASF subversion and git services commented on ISIS-3002:
---

Commit 96b7546444f90d64fcb53e7f6220a62168069880 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=96b7546444 ]

ISIS-3002: adds wildcard for HasInteraction_executionLogEntries mixin

so can inject repository bean


> Bring in extensions/core/outbox-publisher (from incode-platform)
> 
>
> Key: ISIS-3002
> URL: https://issues.apache.org/jira/browse/ISIS-3002
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Extensions
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> and then remove mappings entirely, cf ISIS-2999



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3062) sessionlog extension

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574416#comment-17574416
 ] 

ASF subversion and git services commented on ISIS-3062:
---

Commit 8d64dfd66eafb73043d8fc11c0505ba79bd0057d in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=8d64dfd66e ]

ISIS-3062: SessionLogEntry#causedBy should be optional


> sessionlog extension
> 
>
> Key: ISIS-3062
> URL: https://issues.apache.org/jira/browse/ISIS-3062
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Extensions
>Affects Versions: 2.0.0-M7
>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] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574346#comment-17574346
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 3807ee7d4df0716481f1c6b795048bc892fadda3 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=3807ee7d4d ]

ISIS-3108: removes special case processing, we now always install the facet


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574347#comment-17574347
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 254e0379be4825901a9609342f7bd2b8186e5de8 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=254e0379be ]

ISIS-3108: fixes unit test


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574348#comment-17574348
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit cbb954f6de02e5392538b2b675d976addf7fabf9 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=cbb954f6de ]

Merge branch 'ISIS-3108'


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574344#comment-17574344
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 254e0379be4825901a9609342f7bd2b8186e5de8 in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=254e0379be ]

ISIS-3108: fixes unit test


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574339#comment-17574339
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 6f043889d5e7daac4467c00e84d356b76748750e in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=6f043889d5 ]

ISIS-3108: updates regression test


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574337#comment-17574337
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 77330c42bada206c1f62e0ca83f2941883fe7508 in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=77330c42ba ]

ISIS-3108: fixing unit tests


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574341#comment-17574341
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 3807ee7d4df0716481f1c6b795048bc892fadda3 in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=3807ee7d4d ]

ISIS-3108: removes special case processing, we now always install the facet


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574336#comment-17574336
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 738632b133d74bbe43c3bd05cb0f3defdbe7ca44 in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=738632b133 ]

ISIS-3108: makes EntityPublishingChangeFacet explicit


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574340#comment-17574340
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 378ced296b4cdb2a07da819471991010147e9524 in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=378ced296b ]

Merge branch 'ISIS-3108'


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574335#comment-17574335
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit 810e78e70111af992c13496905023d47d684ab67 in isis's branch 
refs/heads/ISIS-3108 from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=810e78e701 ]

ISIS-3105: ZoneOffset.UTC and ZoneId.of("UTC") result in different
output format;

- that is 'Z' vs 'UTC'

- so we prefer to use ZoneId.of("UTC") for UTC based ZoneDateTime values

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574338#comment-17574338
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit c68e9d0b786b7c8c9f466c387904f18d5efcce30 in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=c68e9d0b78 ]

ISIS-3108: fixing unit tests


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574301#comment-17574301
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 6f043889d5e7daac4467c00e84d356b76748750e in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=6f043889d5 ]

ISIS-3108: updates regression test


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574302#comment-17574302
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 378ced296b4cdb2a07da819471991010147e9524 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=378ced296b ]

Merge branch 'ISIS-3108'


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574298#comment-17574298
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 738632b133d74bbe43c3bd05cb0f3defdbe7ca44 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=738632b133 ]

ISIS-3108: makes EntityPublishingChangeFacet explicit


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574299#comment-17574299
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 77330c42bada206c1f62e0ca83f2941883fe7508 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=77330c42ba ]

ISIS-3108: fixing unit tests


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574300#comment-17574300
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit c68e9d0b786b7c8c9f466c387904f18d5efcce30 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=c68e9d0b78 ]

ISIS-3108: fixing unit tests


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3109) [Wicket Viewer] Wire up ZoneId from Login Page with InteractionContexts

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-3109:
-
Description: Yet InteractionContext.getTimeZone() defaults to 
ZoneId.systemDefault() and is never properly set.  (was: Yet 
InteractionContext.getTimeZone() defaults to ZoneId.systemDefault() an is never 
properly set.)

> [Wicket Viewer] Wire up ZoneId from Login Page with InteractionContexts
> ---
>
> Key: ISIS-3109
> URL: https://issues.apache.org/jira/browse/ISIS-3109
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Viewer Wicket
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> Yet InteractionContext.getTimeZone() defaults to ZoneId.systemDefault() and 
> is never properly set.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574291#comment-17574291
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 1484299e6466ef1f43ec13d06f26f2043254ed3f in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=1484299e64 ]

ISIS-3108: fixing unit tests


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3109) [Wicket Viewer] Wire up ZoneId from Login Page with InteractionContexts

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-3109:
-
Summary: [Wicket Viewer] Wire up ZoneId from Login Page with 
InteractionContexts  (was: [Wicket Viewer] Wire up ZoneId selection from Login 
Page with InteractionContext Creation)

> [Wicket Viewer] Wire up ZoneId from Login Page with InteractionContexts
> ---
>
> Key: ISIS-3109
> URL: https://issues.apache.org/jira/browse/ISIS-3109
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Viewer Wicket
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> Yet InteractionContext.getTimeZone() defaults to ZoneId.systemDefault() an is 
> never properly set.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (ISIS-3109) [Wicket Viewer] Wire up ZoneId selection from Login Page with InteractionContext Creation

2022-08-02 Thread Andi Huber (Jira)
Andi Huber created ISIS-3109:


 Summary: [Wicket Viewer] Wire up ZoneId selection from Login Page 
with InteractionContext Creation
 Key: ISIS-3109
 URL: https://issues.apache.org/jira/browse/ISIS-3109
 Project: Isis
  Issue Type: Bug
  Components: Isis Viewer Wicket
Reporter: Andi Huber
Assignee: Andi Huber
 Fix For: 2.0.0-M8


Yet InteractionContext.getTimeZone() defaults to ZoneId.systemDefault() an is 
never properly set.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574280#comment-17574280
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 7d2d74efbdb3b68076fdda34adccf6236bde19ff in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=7d2d74efbd ]

ISIS-3108: fixing unit tests


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574274#comment-17574274
 ] 

ASF subversion and git services commented on ISIS-3108:
---

Commit 25fa9673030bd82f2838275315f71211576503be in isis's branch 
refs/heads/ISIS-3108 from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=25fa967303 ]

ISIS-3108: makes EntityPublishingChangeFacet explicit


> AuditTrailEntry should not attempt to audit itself (!)
> --
>
> Key: ISIS-3108
> URL: https://issues.apache.org/jira/browse/ISIS-3108
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Critical
> Fix For: 2.0.0-M8
>
>
> currently prevents audit trail from being used.
> Issue is that the EntityPublishingChangeFacet is found to not exist for 
> java.lang.Object, so we then use the default configuration, usually enabled.
> The new design always installs the EntityPublishingChangeFacet, but has a 
> flag to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (ISIS-3108) AuditTrailEntry should not attempt to audit itself (!)

2022-08-02 Thread Daniel Keir Haywood (Jira)
Daniel Keir Haywood created ISIS-3108:
-

 Summary: AuditTrailEntry should not attempt to audit itself (!)
 Key: ISIS-3108
 URL: https://issues.apache.org/jira/browse/ISIS-3108
 Project: Isis
  Issue Type: Bug
Affects Versions: 2.0.0-M7
Reporter: Daniel Keir Haywood
Assignee: Daniel Keir Haywood
 Fix For: 2.0.0-M8


currently prevents audit trail from being used.

Issue is that the EntityPublishingChangeFacet is found to not exist for 
java.lang.Object, so we then use the default configuration, usually enabled.

The new design always installs the EntityPublishingChangeFacet, but has a flag 
to indicate if enabled or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3107) For JDO, autocreate schema, allow multiple placeholders in string

2022-08-02 Thread Andi Huber (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574258#comment-17574258
 ] 

Andi Huber commented on ISIS-3107:
--

So pattern 
"if not exists (select 1 from INFORMATION_SCHEMA.SCHEMATA WHERE SCHEMA_NAME = 
'%1$s') exec('create schema %1$s')" 
should have done the trick as well ;} 

> For JDO, autocreate schema, allow multiple placeholders in string
> -
>
> Key: ISIS-3107
> URL: https://issues.apache.org/jira/browse/ISIS-3107
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Persistence JDO
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Trivial
> Fix For: 2.0.0-M8
>
>
> for example, on SQL Server we need to use a string such as:
> if not exists (select 1 from INFORMATION_SCHEMA.SCHEMATA WHERE SCHEMA_NAME = 
> '%s') exec('create schema %s')
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574254#comment-17574254
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit 810e78e70111af992c13496905023d47d684ab67 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=810e78e701 ]

ISIS-3105: ZoneOffset.UTC and ZoneId.of("UTC") result in different
output format;

- that is 'Z' vs 'UTC'

- so we prefer to use ZoneId.of("UTC") for UTC based ZoneDateTime values

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3091) audit trail (impl EntityPropertyChanges subscriber to persist to DB).

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574241#comment-17574241
 ] 

ASF subversion and git services commented on ISIS-3091:
---

Commit e1764ad1f6a64ab7adda092da9707ac49e296020 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=e1764ad1f6 ]

ISIS-3091: adds back the table name as prefix for indices

also fixes 4 issues of inconsistent semantics for Execution{Log/Outbox}Entry


> audit trail (impl EntityPropertyChanges subscriber to persist to DB).
> -
>
> Key: ISIS-3091
> URL: https://issues.apache.org/jira/browse/ISIS-3091
> Project: Isis
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M7
>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] [Commented] (ISIS-3107) For JDO, autocreate schema, allow multiple placeholders in string

2022-08-02 Thread Andi Huber (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574231#comment-17574231
 ] 

Andi Huber commented on ISIS-3107:
--

Java's String.format(...) allows for referencing arguments by index!
https://stackoverflow.com/questions/1915074/understanding-the-in-javas-format-strings

> For JDO, autocreate schema, allow multiple placeholders in string
> -
>
> Key: ISIS-3107
> URL: https://issues.apache.org/jira/browse/ISIS-3107
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Persistence JDO
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Trivial
> Fix For: 2.0.0-M8
>
>
> for example, on SQL Server we need to use a string such as:
> if not exists (select 1 from INFORMATION_SCHEMA.SCHEMATA WHERE SCHEMA_NAME = 
> '%s') exec('create schema %s')
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3107) For JDO, autocreate schema, allow multiple placeholders in string

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574226#comment-17574226
 ] 

ASF subversion and git services commented on ISIS-3107:
---

Commit b682ecf07976646b236ce131c0f806ecf7e5fa27 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=b682ecf079 ]

ISIS-3107: allows multiple placeholders in create schema template


> For JDO, autocreate schema, allow multiple placeholders in string
> -
>
> Key: ISIS-3107
> URL: https://issues.apache.org/jira/browse/ISIS-3107
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Persistence JDO
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Trivial
> Fix For: 2.0.0-M8
>
>
> for example, on SQL Server we need to use a string such as:
> if not exists (select 1 from INFORMATION_SCHEMA.SCHEMATA WHERE SCHEMA_NAME = 
> '%s') exec('create schema %s')
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (ISIS-3107) For JDO, autocreate schema, allow multiple placeholders in string

2022-08-02 Thread Daniel Keir Haywood (Jira)
Daniel Keir Haywood created ISIS-3107:
-

 Summary: For JDO, autocreate schema, allow multiple placeholders 
in string
 Key: ISIS-3107
 URL: https://issues.apache.org/jira/browse/ISIS-3107
 Project: Isis
  Issue Type: Improvement
  Components: Isis Persistence JDO
Affects Versions: 2.0.0-M7
Reporter: Daniel Keir Haywood
Assignee: Daniel Keir Haywood
 Fix For: 2.0.0-M8


for example, on SQL Server we need to use a string such as:

if not exists (select 1 from INFORMATION_SCHEMA.SCHEMATA WHERE SCHEMA_NAME = 
'%s') exec('create schema %s')

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber closed ISIS-3105.


> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2578) Address known Issues/Limitations for JDO/JPA

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2578:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> Address known Issues/Limitations for JDO/JPA
> 
>
> Key: ISIS-2578
> URL: https://issues.apache.org/jira/browse/ISIS-2578
> Project: Isis
>  Issue Type: Task
>  Components: Isis Core
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> JDO Stack:
>  * DN enhancer supports up to Java 15; Java 16 not supported yet
>  * No injection points resolved on entity collections as fetched by JDO.   
> <<< in isis v1 /DN 4 we used the "org.datanucleus.state.ObjectProvider" 
> plugin point (renamed in DN6 to "org.datanucleus.state.DNStateManager")
>  * Entity Change Tracking not working.
> JPA Stack:
>  * No Entity Change Tracking (Application Layer Integration).
>  * No injection points resolved on entity collections as fetched by JPA.
> SecMan Extension:
>  * Cannot set permissions on mixins, only on their mixees. (eg. 'Clear 
> Hints') -> NOT AN ISSUE



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (ISIS-3103) Separation of Concerns: BookmarkServiceDefault vs SerializingAdapter

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber closed ISIS-3103.


> Separation of Concerns: BookmarkServiceDefault vs SerializingAdapter
> 
>
> Key: ISIS-3103
> URL: https://issues.apache.org/jira/browse/ISIS-3103
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Core
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> Looks like a candidate for separation of concerns, that is bookmarking 
> specifics vs. low-level serialization specifics.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3008) [Wicket Viewer] Pending Parameter Glitches

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-3008:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Wicket Viewer] Pending Parameter Glitches
> --
>
> Key: ISIS-3008
> URL: https://issues.apache.org/jira/browse/ISIS-3008
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Viewer Wicket
>Affects Versions: 2.0.0-M8
>Reporter: Daniel Keir Haywood
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
> Attachments: no-changes.gif
>
>
> Changing (n-1)-th argument clears n-th argument.
> (see attachment)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber resolved ISIS-3105.
--
Resolution: Fixed

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2297) [Ongoing] Mitigate Sonar Code Quality Issues

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2297:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Ongoing] Mitigate Sonar Code Quality Issues
> 
>
> Key: ISIS-2297
> URL: https://issues.apache.org/jira/browse/ISIS-2297
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis CI  Build Scripts
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> Ongoing task: Mitigate Sonar Code Quality Issues



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3048) Suggested UI improvements (after review demo app)

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-3048:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> Suggested UI improvements (after review demo app)
> -
>
> Key: ISIS-3048
> URL: https://issues.apache.org/jira/browse/ISIS-3048
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Viewer Wicket
>Reporter: Johan Doornenbal
>Assignee: Andi Huber
>Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> - menu - actions - dependent arguments - multichoices: lacks spacing line 
> between arguments in pop-up
> - menu -featured - tabdemo: after editing a property on 2nd or 3rd tab, the 
> ui returns to the first tab - I would like it to remain on the tab of the 
> property
> (My personal taste)
> - some black lines maybe too black compared to rest of the page? (Like 
> separation line between headers and collection details)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2445) [Ongoing] CI Maintenance

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2445:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Ongoing] CI Maintenance
> 
>
> Key: ISIS-2445
> URL: https://issues.apache.org/jira/browse/ISIS-2445
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis CI  Build Scripts
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> Ongoing task across releases.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-1659) [Performance] no-arg actions (eg toggle) don't respect config property isRedirectOnlyIfSameObject=false

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-1659:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Performance] no-arg actions (eg toggle) don't respect config property 
> isRedirectOnlyIfSameObject=false
> ---
>
> Key: ISIS-1659
> URL: https://issues.apache.org/jira/browse/ISIS-1659
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Viewer Wicket
>Reporter: Daniel Keir Haywood
>Assignee: Andi Huber
>Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> eg:
> {code}
> public SomeObject toggle() {
> setFlag(! isFlag());
> return this;
> }
> {code}
> will cause a redirect to the same page, even though the same object is being 
> rendered.  
> The reason is because the current viewer implementation does not expose the 
> AjaxRequestTarget.  Need some deep surgery somewhere...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574213#comment-17574213
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit fbb22ebd79abdbb3ef8ed629611ae6ed135bf675 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=fbb22ebd79 ]

ISIS-3105: value-semantics: honor ZoneId name if any (affects
formatting)

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3061) [Wish] "General" field allowed to named as ObjectType name instead. (first Tab on wicket UI)

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-3061:
--
Fix Version/s: 2.1
   (was: 2.0.0-M8)

> [Wish] "General" field allowed to named as ObjectType name instead. (first 
> Tab on wicket UI)
> 
>
> Key: ISIS-3061
> URL: https://issues.apache.org/jira/browse/ISIS-3061
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Viewer Wicket
>Reporter: Dhruv Gohil
>Priority: Minor
> Fix For: 2.1
>
> Attachments: Screenshot from 2022-05-23 16-35-21.png
>
>
> It would be preferable that the tab name used for the first tab is the human 
> friendly name of the object's type, ie "Simple Object" (or in other cases, 
> "Customer", "Order", "Product" etc) rather than always the text "General" 
> From non-technical user's perspective landing on app's bookmarked link takes 
> user to directly entity page, and nowhere he is able to see the name of the 
> entity (obviously except in url and tool-tip on hover)
> Although the current behavior  is very from very early days, and hopefully as 
> its a display text field and no-one should be dependent on it for business 
> logic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3014) Enum typed property value display is incorrect

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-3014:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> Enum typed property value display is incorrect
> --
>
> Key: ISIS-3014
> URL: https://issues.apache.org/jira/browse/ISIS-3014
> Project: Isis
>  Issue Type: Question
>  Components: Wicket Viewer
>Affects Versions: 2.0.0-M7
>Reporter: Miklós Győrfi
>Priority: Major
>  Labels: TestCaseRequired
> Fix For: 2.0.0-RC1
>
>
>  
> In Isis enum values can have title (@Title) property to display user friendly.
> For example:
>  
>  
> {code:java}
> public enum PublicationMode {
>   jupyter_notebook("Jupyter notebook"),
>   jupyter_notebook_pdf_email("Jupyter notebook PDF fájl levélhez"),
>   site_json_data("Hely JSON adata");
>   private final String title;
>   PublicationMode(String title) {
> this.title = title;
>   }
>   @Title
>   public String getTitle() {
> return title;
>   }
> } {code}
> It works very well everywhere in Isis, except:
>  
> Wicket viewer uses StringPanel to display it (according to 
> ValueChoicesSelect2PanelFactory).
>  * It would be better to display it as ValueFallbackPanel instead of 
> StringPanel. in view mode, ValueChoicesSelect2Panel works well in edit mode.
>  * ValueFallbackPanel  should display ManagedObjects.titleOf(objectAdapter), 
> overriding newTextFieldValueModel and return an overridden kind of 
> TextFieldValueModel for example (which is not possible now, because 
> it is a final method). Other solution to create a good converter and facet.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3014) Enum typed property value display is incorrect

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-3014:
--
Labels: TestCaseRequired  (was: )

> Enum typed property value display is incorrect
> --
>
> Key: ISIS-3014
> URL: https://issues.apache.org/jira/browse/ISIS-3014
> Project: Isis
>  Issue Type: Question
>  Components: Wicket Viewer
>Affects Versions: 2.0.0-M7
>Reporter: Miklós Győrfi
>Priority: Major
>  Labels: TestCaseRequired
> Fix For: 2.0.0-M8
>
>
>  
> In Isis enum values can have title (@Title) property to display user friendly.
> For example:
>  
>  
> {code:java}
> public enum PublicationMode {
>   jupyter_notebook("Jupyter notebook"),
>   jupyter_notebook_pdf_email("Jupyter notebook PDF fájl levélhez"),
>   site_json_data("Hely JSON adata");
>   private final String title;
>   PublicationMode(String title) {
> this.title = title;
>   }
>   @Title
>   public String getTitle() {
> return title;
>   }
> } {code}
> It works very well everywhere in Isis, except:
>  
> Wicket viewer uses StringPanel to display it (according to 
> ValueChoicesSelect2PanelFactory).
>  * It would be better to display it as ValueFallbackPanel instead of 
> StringPanel. in view mode, ValueChoicesSelect2Panel works well in edit mode.
>  * ValueFallbackPanel  should display ManagedObjects.titleOf(objectAdapter), 
> overriding newTextFieldValueModel and return an overridden kind of 
> TextFieldValueModel for example (which is not possible now, because 
> it is a final method). Other solution to create a good converter and facet.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3044) [kroviz] Fix Various UI Glitches

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-3044:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [kroviz] Fix Various UI Glitches
> 
>
> Key: ISIS-3044
> URL: https://issues.apache.org/jira/browse/ISIS-3044
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Client Kroviz
>Affects Versions: 2.0.0-M7
>Reporter: Jörg Rade
>Assignee: Jörg Rade
>Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> * LogEntry.type empty for menuBars
>  * Blob sizes are not shown



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3074) Shiro - Enhanced Wildcard Permissions Don't Work as Expected

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-3074:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> Shiro - Enhanced Wildcard Permissions Don't Work as Expected
> 
>
> Key: ISIS-3074
> URL: https://issues.apache.org/jira/browse/ISIS-3074
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Security Shiro
>Affects Versions: 2.0.0-M7
>Reporter: Jörg Rade
>Priority: Major
> Fix For: 2.0.0-RC1
>
> Attachments: knife_menu_with_x_prefix.png, knife_menu_without_reg.png
>
>
> With (shiro.ini):
> {code}
> securityManager.realms = $iniRealm
> permissionResolver = 
> org.apache.isis.security.shiro.authorization.IsisPermissionResolver
> iniRealm.permissionResolver = $permissionResolver
> [...]
> guest_role = !knife:Endpoints,\
>  !knife:Releases,\
>  !knife:Configurations,\
>  !knife:RuntimeEnvironments,\
>  !knife:Comparisons,\
>  !knife:ConfigComparisons,\
>  !knife:ReleaseComparisons,\
>  !knife:ServiceComparisons,\
>  !knife:Diagrams,\
>  *
> {code}
> I get  !knife_menu_without_reg.png! 
> And with a prefix (be it "reg/", "xxx/", or "x/") I get an output that's 
> closer to my expectations:
>  !knife_menu_with_x_prefix.png! 
> Nevertheless, my expectation is, that
> * RuntimeEnvironments,
> * Comparisons, and
> * Diagrams 
> would be omitted as well.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3029) Schema "isisextensionssecman" does not exists

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574211#comment-17574211
 ] 

ASF subversion and git services commented on ISIS-3029:
---

Commit ad483ab8b8d83fda83f48d903bb22edf239072b5 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=ad483ab8b8 ]

ISIS-3029: test fixes

> Schema "isisextensionssecman" does not exists
> -
>
> Key: ISIS-3029
> URL: https://issues.apache.org/jira/browse/ISIS-3029
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Extensions SecMan
>Affects Versions: 2.0.0-M7
>Reporter: Han Hui Wen 
>Priority: Major
>  Labels: TestCaseRequired
> Fix For: 2.0.0-RC1
>
>
> I use Postgresql .when I try ISIS secman extension ,find following issue :
>  
> Call: CREATE TABLE isisExtensionsSecman.ApplicationUserRoles (roleId BIGINT 
> NOT NULL, userId BIGINT NOT NULL, PRIMARY KEY (roleId, userId))
> Query: DataModifyQuery(sql="CREATE TABLE 
> isisExtensionsSecman.ApplicationUserRoles (roleId BIGINT NOT NULL, userId 
> BIGINT NOT NULL, PRIMARY KEY (roleId, userId))")
> [EL Warning]: 2022-04-27 14:08:56.375--ServerSession(1942100755)--Exception 
> [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.7.10.v20211216-fe64cd39c3): 
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: Error 
> schema"isisextensionssecman"  does not exits .
>  
> Anctullay I have  created isisextensionssecman in Postgresql Database . Seems 
> it's cause by Postgres  names case sensitive issue .
>  
> when I change the configuration as following according to the document :
> [https://isis.apache.org/security/2.0.0-M7/secman/setting-up.html#examples]
>  
> isis:
>     persistence:
>         schema:
>               auto-create-schemas: abdb
> It's still has  the issue , seems isisextensionssecman is hard coding in 
> program .
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (ISIS-3041) [Ongoing] Site/Doc Maintenance

2022-08-02 Thread Daniel Keir Haywood (Jira)


 [ 
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: Jörg Rade
>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-3035) [Wish] Log Stacktrace alongside ERROR to Console

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-3035:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Wish] Log Stacktrace alongside ERROR to Console
> 
>
> Key: ISIS-3035
> URL: https://issues.apache.org/jira/browse/ISIS-3035
> Project: Isis
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M7
>Reporter: Jörg Rade
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> I have an issue with a (kind of) swallowed exception. 
> IsisInteraction.executeInternal stumbles over an
> {code:java}
> org.springframework.dao.IncorrectResultSizeDataAccessException: More than one 
> result was returned from Query.getSingleResult(); nested exception is 
> javax.persistence.NonUniqueResultException: More than one result was returned 
> from Query.getSingleResult(){code}
> The (Wicket) UI shows:
> {code:java}
> [object not found]: object not found (incorrect result size data access 
> exception): More than one result was returned from Query.getSingleResult() 
> {code}
> Console shows:
> {code:java}
> 2022-05-03 12:08:07.051 ERROR 22432 — [nio-8080-exec-4] 
> o.a.i.c.i.s.IsisInteraction : failed to execute an interaction
> {code}
>  
> I would prefer to have the stacktrace logged to console as well.
> c.f. https://the-asf.slack.com/archives/CFC42LWBV/p1651573266998419



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2996) [kroviz] Checksum validation failed -> isis-client-kroviz-2.0.0-M7.pom/jar

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-2996:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [kroviz] Checksum validation failed -> isis-client-kroviz-2.0.0-M7.pom/jar
> --
>
> Key: ISIS-2996
> URL: https://issues.apache.org/jira/browse/ISIS-2996
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Client Kroviz
>Affects Versions: 2.0.0-M7
>Reporter: Jörg Rade
>Assignee: Jörg Rade
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> {code}
> Downloading from github: 
> https://github.com/orgs/apache/packages?repo_name=isis/org/apache/isis/incubator/clients/isis-client-kroviz/2.0.0-M7/isis-client-kroviz-2.0.0-M7.pom
> [WARNING] Checksum validation failed, expected  2957fa1aa94bb336f1dde747283c052fdf453828 from github for 
> https://github.com/orgs/apache/packages?repo_name=isis/org/apache/isis/incubator/clients/isis-client-kroviz/2.0
> .0-M7/isis-client-kroviz-2.0.0-M7.pom
> [WARNING] Could not validate integrity of download from 
> https://github.com/orgs/apache/packages?repo_name=isis/org/apache/isis/incubator/clients/isis-client-kroviz/2.0.0-M7/isis-client-kroviz-2.0.0-M7.pom
> org.eclipse.aether.transfer.ChecksumFailureException: Checksum validation 
> failed, expected  at 
> org.eclipse.aether.connector.basic.ChecksumValidator.validateExternalChecksums
>  (ChecksumValidator.java:174)
> at org.eclipse.aether.connector.basic.ChecksumValidator.validate 
> (ChecksumValidator.java:103)
> at 
> org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask
>  (BasicRepositoryConnector.java:460)
> at 
> org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run 
> (BasicRepositoryConnector.java:364)
> at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run 
> (RunnableErrorForwarder.java:75)
> at 
> org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute
>  (BasicRepositoryConnector.java:628)
> at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get 
> (BasicRepositoryConnector.java:262)
> at 
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads 
> (DefaultArtifactResolver.java:514)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve 
> (DefaultArtifactResolver.java:402)
> at 
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts 
> (DefaultArtifactResolver.java:229)
> at 
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact 
> (DefaultArtifactResolver.java:207)
> at 
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom 
> (DefaultArtifactDescriptorReader.java:244)
> at 
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor
>  (DefaultArtifactDescriptorReader.java:175)
> at 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.resolveCachedArtifactDescriptor
>  (DefaultDependencyCollector.java:538)
> at 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.getArtifactDescriptorResult
>  (DefaultDependencyCollector.java:523)
> at 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
>  (DefaultDependencyCollector.java:410)
> at 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency
>  (DefaultDependencyCollector.java:362)
> at 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process 
> (DefaultDependencyCollector.java:349)
> at 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.collectDependencies
>  (DefaultDependencyCollector.java:254)
> at 
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies 
> (DefaultRepositorySystem.java:284)
> at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve 
> (DefaultProjectDependenciesResolver.java:170)
> at 
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
>  (LifecycleDependencyResolver.java:243)
> at 
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
>  (LifecycleDependencyResolver.java:147)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
>  (MojoExecutor.java:248)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:202)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:148)
> at 
> 

[jira] [Updated] (ISIS-2953) [kroviz] Improve Branding

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-2953:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [kroviz] Improve Branding
> -
>
> Key: ISIS-2953
> URL: https://issues.apache.org/jira/browse/ISIS-2953
> Project: Isis
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M6
>Reporter: Jörg Rade
>Assignee: Jörg Rade
>Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> * use small image for MenuBar
> * in case of missing logo, use sensible default 
> * overload fixed values for colors, fonts, sizes with values form user 
> specified file (c.f. theme in the wicket viewer)
> * refactor About dialog
> * refactor Samples



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2851) Basic Types / Bytes

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-2851:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> Basic Types / Bytes
> ---
>
> Key: ISIS-2851
> URL: https://issues.apache.org/jira/browse/ISIS-2851
> Project: Isis
>  Issue Type: Sub-task
>  Components: Isis Client Kroviz
>Reporter: Jörg Rade
>Assignee: Jörg Rade
>Priority: Minor
> Fix For: 2.0.0-RC1
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (ISIS-3029) Schema "isisextensionssecman" does not exists

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood reassigned ISIS-3029:
-

Assignee: (was: Daniel Keir Haywood)

> Schema "isisextensionssecman" does not exists
> -
>
> Key: ISIS-3029
> URL: https://issues.apache.org/jira/browse/ISIS-3029
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Extensions SecMan
>Affects Versions: 2.0.0-M7
>Reporter: Han Hui Wen 
>Priority: Major
>  Labels: TestCaseRequired
> Fix For: 2.0.0-RC1
>
>
> I use Postgresql .when I try ISIS secman extension ,find following issue :
>  
> Call: CREATE TABLE isisExtensionsSecman.ApplicationUserRoles (roleId BIGINT 
> NOT NULL, userId BIGINT NOT NULL, PRIMARY KEY (roleId, userId))
> Query: DataModifyQuery(sql="CREATE TABLE 
> isisExtensionsSecman.ApplicationUserRoles (roleId BIGINT NOT NULL, userId 
> BIGINT NOT NULL, PRIMARY KEY (roleId, userId))")
> [EL Warning]: 2022-04-27 14:08:56.375--ServerSession(1942100755)--Exception 
> [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.7.10.v20211216-fe64cd39c3): 
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: Error 
> schema"isisextensionssecman"  does not exits .
>  
> Anctullay I have  created isisextensionssecman in Postgresql Database . Seems 
> it's cause by Postgres  names case sensitive issue .
>  
> when I change the configuration as following according to the document :
> [https://isis.apache.org/security/2.0.0-M7/secman/setting-up.html#examples]
>  
> isis:
>     persistence:
>         schema:
>               auto-create-schemas: abdb
> It's still has  the issue , seems isisextensionssecman is hard coding in 
> program .
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2837) [kroviz] Execute Integration Tests against Docker Image (Demo)

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-2837:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [kroviz] Execute Integration Tests against Docker Image (Demo)
> --
>
> Key: ISIS-2837
> URL: https://issues.apache.org/jira/browse/ISIS-2837
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Client Kroviz
>Reporter: Jörg Rade
>Assignee: Jörg Rade
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> Currently kroviz integration tests simply check, if an application is 
> available at localhost:8080.
> If the app is not available, tests are skipped.
> Ensure a docker image is running at this address, skip the check and always 
> execute tests
> c.f. 
> https://info.michael-simons.eu/2016/08/25/integration-testing-with-docker-and-maven/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3029) Schema "isisextensionssecman" does not exists

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-3029:
--
Labels: TestCaseRequired  (was: )

> Schema "isisextensionssecman" does not exists
> -
>
> Key: ISIS-3029
> URL: https://issues.apache.org/jira/browse/ISIS-3029
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Extensions SecMan
>Affects Versions: 2.0.0-M7
>Reporter: Han Hui Wen 
>Assignee: Daniel Keir Haywood
>Priority: Major
>  Labels: TestCaseRequired
> Fix For: 2.0.0-RC1
>
>
> I use Postgresql .when I try ISIS secman extension ,find following issue :
>  
> Call: CREATE TABLE isisExtensionsSecman.ApplicationUserRoles (roleId BIGINT 
> NOT NULL, userId BIGINT NOT NULL, PRIMARY KEY (roleId, userId))
> Query: DataModifyQuery(sql="CREATE TABLE 
> isisExtensionsSecman.ApplicationUserRoles (roleId BIGINT NOT NULL, userId 
> BIGINT NOT NULL, PRIMARY KEY (roleId, userId))")
> [EL Warning]: 2022-04-27 14:08:56.375--ServerSession(1942100755)--Exception 
> [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.7.10.v20211216-fe64cd39c3): 
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: Error 
> schema"isisextensionssecman"  does not exits .
>  
> Anctullay I have  created isisextensionssecman in Postgresql Database . Seems 
> it's cause by Postgres  names case sensitive issue .
>  
> when I change the configuration as following according to the document :
> [https://isis.apache.org/security/2.0.0-M7/secman/setting-up.html#examples]
>  
> isis:
>     persistence:
>         schema:
>               auto-create-schemas: abdb
> It's still has  the issue , seems isisextensionssecman is hard coding in 
> program .
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2984) @GeneratedValue(strategy = GenerationType.SEQUENCE) no longer works after migrating to 2.0.0.M7

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-2984:
--
Labels: TestCaseRequired  (was: )

> @GeneratedValue(strategy = GenerationType.SEQUENCE) no longer works after 
> migrating to 2.0.0.M7
> ---
>
> Key: ISIS-2984
> URL: https://issues.apache.org/jira/browse/ISIS-2984
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Persistence JPA
>Affects Versions: 2.0.0-M7
>Reporter: Hao S
>Priority: Major
>  Labels: TestCaseRequired
> Fix For: 2.0.0-RC1
>
>
> DB: mysql 8
> Tested project: Demo App SimpleApp 2.0.0.M7
> When this is used:
> {code:java}
> GenerationType.SEQUENCE{code}
> Error:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: The persistence layer does not 
> recognize given object of type domainapp.modules.simple.dom.so.SimpleObject, 
> meaning the object has no identifier that associates it with the persistence 
> layer. (most likely, because the object is detached, eg. was not persisted 
> after being new-ed up)
>     at 
> org.apache.isis.commons.internal.exceptions._Exceptions.illegalArgument(_Exceptions.java:79)
>  ~[isis-commons-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.persistence.jpa.integration.entity.JpaEntityFacetFactory$JpaEntityFacet.identifierFor(JpaEntityFacetFactory.java:135)
>  ~[isis-persistence-jpa-integration-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.core.metamodel.objectmanager.ObjectManager.autoBookmarked(ObjectManager.java:207)
>  ~[isis-core-metamodel-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.core.metamodel.objectmanager.ObjectManager.adapt(ObjectManager.java:158)
>  ~[isis-core-metamodel-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.core.metamodel.objectmanager.ObjectManager.adapt(ObjectManager.java:130)
>  ~[isis-core-metamodel-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.persistence.jpa.applib.integration.IsisEntityListener.onPrePersist(IsisEntityListener.java:73)
>  ~[isis-persistence-jpa-applib-2.0.0-M7.jar:2.0.0-M7]
>     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:?]
>     at 
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  ~[?:?]
>     at 
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:?]
>     at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
>     at 
> org.eclipse.persistence.internal.security.PrivilegedAccessHelper.invokeMethod(PrivilegedAccessHelper.java:530)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListener.invokeMethod(EntityListener.java:322)
>  ~[org.eclipse.persistence.jpa-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListener.invokeMethod(EntityListener.java:346)
>  ~[org.eclipse.persistence.jpa-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListener.prePersist(EntityListener.java:453)
>  ~[org.eclipse.persistence.jpa-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.descriptors.DescriptorEventManager.notifyListener(DescriptorEventManager.java:746)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.descriptors.DescriptorEventManager.notifyEJB30Listeners(DescriptorEventManager.java:672)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.descriptors.DescriptorEventManager.executeEvent(DescriptorEventManager.java:233)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNewObjectClone(UnitOfWorkImpl.java:4468)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNotRegisteredNewObjectForPersist(UnitOfWorkImpl.java:4445)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.registerNotRegisteredNewObjectForPersist(RepeatableWriteUnitOfWork.java:523)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNewObjectForPersist(UnitOfWorkImpl.java:4387)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]{code}
> Basically the entity does not get a auto-generated primary key. This worked 
> before in 2.0.0.M6
> Thanks!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2984) @GeneratedValue(strategy = GenerationType.SEQUENCE) no longer works after migrating to 2.0.0.M7

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-2984:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> @GeneratedValue(strategy = GenerationType.SEQUENCE) no longer works after 
> migrating to 2.0.0.M7
> ---
>
> Key: ISIS-2984
> URL: https://issues.apache.org/jira/browse/ISIS-2984
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Persistence JPA
>Affects Versions: 2.0.0-M7
>Reporter: Hao S
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> DB: mysql 8
> Tested project: Demo App SimpleApp 2.0.0.M7
> When this is used:
> {code:java}
> GenerationType.SEQUENCE{code}
> Error:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: The persistence layer does not 
> recognize given object of type domainapp.modules.simple.dom.so.SimpleObject, 
> meaning the object has no identifier that associates it with the persistence 
> layer. (most likely, because the object is detached, eg. was not persisted 
> after being new-ed up)
>     at 
> org.apache.isis.commons.internal.exceptions._Exceptions.illegalArgument(_Exceptions.java:79)
>  ~[isis-commons-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.persistence.jpa.integration.entity.JpaEntityFacetFactory$JpaEntityFacet.identifierFor(JpaEntityFacetFactory.java:135)
>  ~[isis-persistence-jpa-integration-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.core.metamodel.objectmanager.ObjectManager.autoBookmarked(ObjectManager.java:207)
>  ~[isis-core-metamodel-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.core.metamodel.objectmanager.ObjectManager.adapt(ObjectManager.java:158)
>  ~[isis-core-metamodel-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.core.metamodel.objectmanager.ObjectManager.adapt(ObjectManager.java:130)
>  ~[isis-core-metamodel-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.persistence.jpa.applib.integration.IsisEntityListener.onPrePersist(IsisEntityListener.java:73)
>  ~[isis-persistence-jpa-applib-2.0.0-M7.jar:2.0.0-M7]
>     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:?]
>     at 
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  ~[?:?]
>     at 
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:?]
>     at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
>     at 
> org.eclipse.persistence.internal.security.PrivilegedAccessHelper.invokeMethod(PrivilegedAccessHelper.java:530)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListener.invokeMethod(EntityListener.java:322)
>  ~[org.eclipse.persistence.jpa-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListener.invokeMethod(EntityListener.java:346)
>  ~[org.eclipse.persistence.jpa-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListener.prePersist(EntityListener.java:453)
>  ~[org.eclipse.persistence.jpa-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.descriptors.DescriptorEventManager.notifyListener(DescriptorEventManager.java:746)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.descriptors.DescriptorEventManager.notifyEJB30Listeners(DescriptorEventManager.java:672)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.descriptors.DescriptorEventManager.executeEvent(DescriptorEventManager.java:233)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNewObjectClone(UnitOfWorkImpl.java:4468)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNotRegisteredNewObjectForPersist(UnitOfWorkImpl.java:4445)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.registerNotRegisteredNewObjectForPersist(RepeatableWriteUnitOfWork.java:523)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNewObjectForPersist(UnitOfWorkImpl.java:4387)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]{code}
> Basically the entity does not get a auto-generated primary key. This worked 
> before in 2.0.0.M6
> Thanks!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (ISIS-2960) jdo + jpa : duplicate primary key exception is not propagated to Wicket viewer

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood closed ISIS-2960.
-
Resolution: Fixed

> jdo + jpa : duplicate primary key exception is not propagated to Wicket viewer
> --
>
> Key: ISIS-2960
> URL: https://issues.apache.org/jira/browse/ISIS-2960
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Persistence JDO, Isis Persistence JPA, Isis Viewer 
> Wicket
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Priority: Minor
> Fix For: 2.0.0-M8
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-2984) @GeneratedValue(strategy = GenerationType.SEQUENCE) no longer works after migrating to 2.0.0.M7

2022-08-02 Thread Daniel Keir Haywood (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574207#comment-17574207
 ] 

Daniel Keir Haywood commented on ISIS-2984:
---

Could you provide an example app please on github demonstrating the issue?

please use a recent nightly.

Thx!

 

> @GeneratedValue(strategy = GenerationType.SEQUENCE) no longer works after 
> migrating to 2.0.0.M7
> ---
>
> Key: ISIS-2984
> URL: https://issues.apache.org/jira/browse/ISIS-2984
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Persistence JPA
>Affects Versions: 2.0.0-M7
>Reporter: Hao S
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> DB: mysql 8
> Tested project: Demo App SimpleApp 2.0.0.M7
> When this is used:
> {code:java}
> GenerationType.SEQUENCE{code}
> Error:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: The persistence layer does not 
> recognize given object of type domainapp.modules.simple.dom.so.SimpleObject, 
> meaning the object has no identifier that associates it with the persistence 
> layer. (most likely, because the object is detached, eg. was not persisted 
> after being new-ed up)
>     at 
> org.apache.isis.commons.internal.exceptions._Exceptions.illegalArgument(_Exceptions.java:79)
>  ~[isis-commons-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.persistence.jpa.integration.entity.JpaEntityFacetFactory$JpaEntityFacet.identifierFor(JpaEntityFacetFactory.java:135)
>  ~[isis-persistence-jpa-integration-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.core.metamodel.objectmanager.ObjectManager.autoBookmarked(ObjectManager.java:207)
>  ~[isis-core-metamodel-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.core.metamodel.objectmanager.ObjectManager.adapt(ObjectManager.java:158)
>  ~[isis-core-metamodel-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.core.metamodel.objectmanager.ObjectManager.adapt(ObjectManager.java:130)
>  ~[isis-core-metamodel-2.0.0-M7.jar:2.0.0-M7]
>     at 
> org.apache.isis.persistence.jpa.applib.integration.IsisEntityListener.onPrePersist(IsisEntityListener.java:73)
>  ~[isis-persistence-jpa-applib-2.0.0-M7.jar:2.0.0-M7]
>     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:?]
>     at 
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  ~[?:?]
>     at 
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:?]
>     at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
>     at 
> org.eclipse.persistence.internal.security.PrivilegedAccessHelper.invokeMethod(PrivilegedAccessHelper.java:530)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListener.invokeMethod(EntityListener.java:322)
>  ~[org.eclipse.persistence.jpa-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListener.invokeMethod(EntityListener.java:346)
>  ~[org.eclipse.persistence.jpa-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListener.prePersist(EntityListener.java:453)
>  ~[org.eclipse.persistence.jpa-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.descriptors.DescriptorEventManager.notifyListener(DescriptorEventManager.java:746)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.descriptors.DescriptorEventManager.notifyEJB30Listeners(DescriptorEventManager.java:672)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.descriptors.DescriptorEventManager.executeEvent(DescriptorEventManager.java:233)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNewObjectClone(UnitOfWorkImpl.java:4468)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNotRegisteredNewObjectForPersist(UnitOfWorkImpl.java:4445)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.registerNotRegisteredNewObjectForPersist(RepeatableWriteUnitOfWork.java:523)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]
>     at 
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNewObjectForPersist(UnitOfWorkImpl.java:4387)
>  ~[org.eclipse.persistence.core-2.7.10.jar:?]{code}
> Basically the entity does not get a auto-generated primary key. This worked 
> before in 2.0.0.M6
> Thanks!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-2960) jdo + jpa : duplicate primary key exception is not propagated to Wicket viewer

2022-08-02 Thread Daniel Keir Haywood (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574206#comment-17574206
 ] 

Daniel Keir Haywood commented on ISIS-2960:
---

This seems to be working ok, don't know when the fix came in.

> jdo + jpa : duplicate primary key exception is not propagated to Wicket viewer
> --
>
> Key: ISIS-2960
> URL: https://issues.apache.org/jira/browse/ISIS-2960
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Persistence JDO, Isis Persistence JPA, Isis Viewer 
> Wicket
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Priority: Minor
> Fix For: 2.0.0-M8
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3029) Schema "isisextensionssecman" does not exists

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood updated ISIS-3029:
--
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> Schema "isisextensionssecman" does not exists
> -
>
> Key: ISIS-3029
> URL: https://issues.apache.org/jira/browse/ISIS-3029
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Extensions SecMan
>Affects Versions: 2.0.0-M7
>Reporter: Han Hui Wen 
>Assignee: Daniel Keir Haywood
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> I use Postgresql .when I try ISIS secman extension ,find following issue :
>  
> Call: CREATE TABLE isisExtensionsSecman.ApplicationUserRoles (roleId BIGINT 
> NOT NULL, userId BIGINT NOT NULL, PRIMARY KEY (roleId, userId))
> Query: DataModifyQuery(sql="CREATE TABLE 
> isisExtensionsSecman.ApplicationUserRoles (roleId BIGINT NOT NULL, userId 
> BIGINT NOT NULL, PRIMARY KEY (roleId, userId))")
> [EL Warning]: 2022-04-27 14:08:56.375--ServerSession(1942100755)--Exception 
> [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.7.10.v20211216-fe64cd39c3): 
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: Error 
> schema"isisextensionssecman"  does not exits .
>  
> Anctullay I have  created isisextensionssecman in Postgresql Database . Seems 
> it's cause by Postgres  names case sensitive issue .
>  
> when I change the configuration as following according to the document :
> [https://isis.apache.org/security/2.0.0-M7/secman/setting-up.html#examples]
>  
> isis:
>     persistence:
>         schema:
>               auto-create-schemas: abdb
> It's still has  the issue , seems isisextensionssecman is hard coding in 
> program .
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (ISIS-3064) Change schema for secman to "isisExtSecman", so consistent with namespace.

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood closed ISIS-3064.
-
Resolution: Fixed

> Change schema for secman to "isisExtSecman", so consistent with namespace.
> --
>
> Key: ISIS-3064
> URL: https://issues.apache.org/jira/browse/ISIS-3064
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Extensions SecMan
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Trivial
> Fix For: 2.0.0-M8
>
>
> and review other extensions' schemas also.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3064) Change schema for secman to "isisExtSecman", so consistent with namespace.

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574204#comment-17574204
 ] 

ASF subversion and git services commented on ISIS-3064:
---

Commit e0c991f576188702261f5e029a9c6f6cd7f89632 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=e0c991f576 ]

ISIS-3064: makes schema for secman consistent with other extensions


> Change schema for secman to "isisExtSecman", so consistent with namespace.
> --
>
> Key: ISIS-3064
> URL: https://issues.apache.org/jira/browse/ISIS-3064
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Extensions SecMan
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Trivial
> Fix For: 2.0.0-M8
>
>
> and review other extensions' schemas also.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (ISIS-3104) factor out Object_clearHints into own module for wicket applib

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood closed ISIS-3104.
-
Resolution: Fixed

> factor out Object_clearHints into own module for wicket applib
> --
>
> Key: ISIS-3104
> URL: https://issues.apache.org/jira/browse/ISIS-3104
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Viewer Wicket
>Affects Versions: 2.0.0-M7
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Minor
> Fix For: 2.0.0-M8
>
>
> also ... regression tests for layout



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574191#comment-17574191
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit 716dae724566732d74f82695f5cd874cb6724c56 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=716dae7245 ]

ISIS-3105: optimization: precalc DELIMITING_WHITESPACE_PATTERN

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574190#comment-17574190
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit aedf2be11286b194d7989b4609623fd890546246 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=aedf2be112 ]

ISIS-3105: adds support for parsing of incomplete temporal strings

- eg. missing zone/offset info or less than 9 digits for fractional
seconds

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574182#comment-17574182
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit 876ffb62673b9cde6c70241b8197a06c8050e5e5 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=876ffb6267 ]

ISIS-3105: consolidate temporal samplers for testing (2)

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574180#comment-17574180
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit 84b195fa982d179d36576644f9bab9ff1aee3bd4 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=84b195fa98 ]

ISIS-3105: consolidate temporal samplers for testing

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574169#comment-17574169
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit 7b6d82acc51bade79ddbbf87d52f3319633935a2 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=7b6d82acc5 ]

ISIS-3105: adds temporal to string conversion tests

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574161#comment-17574161
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit bd83cde4d8a18abce949b5d5a7c71144f24c31d5 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=bd83cde4d8 ]

ISIS-3105: keep nano-seconds when converting temporals to string

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3106) Preserve the @ActionLayout(position) correctly, eg for Object_clearHints

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574159#comment-17574159
 ] 

ASF subversion and git services commented on ISIS-3106:
---

Commit 360bdcaa7f5d1b0680cbdc41143378e0f3c58f26 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=360bdcaa7f ]

ISIS-3106: updates metamodel.xml.zip (regr. tests)

> Preserve the @ActionLayout(position) correctly, eg for Object_clearHints
> 
>
> Key: ISIS-3106
> URL: https://issues.apache.org/jira/browse/ISIS-3106
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Core
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Minor
> Fix For: 2.0.0-M8
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (ISIS-3106) Preserve the @ActionLayout(position) correctly, eg for Object_clearHints

2022-08-02 Thread Daniel Keir Haywood (Jira)


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

Daniel Keir Haywood closed ISIS-3106.
-
Resolution: Fixed

> Preserve the @ActionLayout(position) correctly, eg for Object_clearHints
> 
>
> Key: ISIS-3106
> URL: https://issues.apache.org/jira/browse/ISIS-3106
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Core
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Minor
> Fix For: 2.0.0-M8
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574158#comment-17574158
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit 03990463070e31170388d18dead2b54bc5fc3ee7 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=0399046307 ]

ISIS-3105: de-duplicate time conversion code

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3106) Preserve the @ActionLayout(position) correctly, eg for Object_clearHints

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574120#comment-17574120
 ] 

ASF subversion and git services commented on ISIS-3106:
---

Commit f29865af1d4f6c0c28d6e558b0eb1ea2044eefc8 in isis's branch 
refs/heads/master from Dan Haywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=f29865af1d ]

ISIS-3106: fixes handling of @ActionLayout(position)

also adds descriptions for all of the mixins


> Preserve the @ActionLayout(position) correctly, eg for Object_clearHints
> 
>
> Key: ISIS-3106
> URL: https://issues.apache.org/jira/browse/ISIS-3106
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Core
>Reporter: Daniel Keir Haywood
>Assignee: Daniel Keir Haywood
>Priority: Minor
> Fix For: 2.0.0-M8
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (ISIS-3106) Preserve the @ActionLayout(position) correctly, eg for Object_clearHints

2022-08-02 Thread Daniel Keir Haywood (Jira)
Daniel Keir Haywood created ISIS-3106:
-

 Summary: Preserve the @ActionLayout(position) correctly, eg for 
Object_clearHints
 Key: ISIS-3106
 URL: https://issues.apache.org/jira/browse/ISIS-3106
 Project: Isis
  Issue Type: Bug
  Components: Isis Core
Reporter: Daniel Keir Haywood
Assignee: Daniel Keir Haywood
 Fix For: 2.0.0-M8






--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574119#comment-17574119
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit fe3a1b6fcda466ee5d4e9be3f7d14e7244e88492 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=fe3a1b6fcd ]

ISIS-3105: JPA: adds missing mapping for OffsetDateTime

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574116#comment-17574116
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit f212e6fc7e3cb0858c9ad6cfa482d1890130301f in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=f212e6fc7e ]

ISIS-3105: JDO: adds missing mapping for OffsetDateTime

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ISIS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574111#comment-17574111
 ] 

ASF subversion and git services commented on ISIS-3105:
---

Commit 2b21b46999f85a83703c9d42dbba55161888ba86 in isis's branch 
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=2b21b46999 ]

ISIS-3105: minor: some code formatting

> Support for persisting Temporal Types with Zone/Offset Information
> --
>
> Key: ISIS-3105
> URL: https://issues.apache.org/jira/browse/ISIS-3105
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Persistence JDO, Isis Persistence JPA
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M8
>
>
> What I've found regarding zone/offset information support:
> * MariaDB ... no
> * PostgreSQL ... no
> * MySQL ... no
> * Microsoft SQL Server ... yes
> * Oracle DB ... yes
> * H2 ... yes
> The sensible thing to do is to provide a custom type mapping for JDO and JPA 
> in support of zone/offset temporals, by adding a secondary column that holds 
> the zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (ISIS-3105) Support for persisting Temporal Types with Zone/Offset Information

2022-08-02 Thread Andi Huber (Jira)
Andi Huber created ISIS-3105:


 Summary: Support for persisting Temporal Types with Zone/Offset 
Information
 Key: ISIS-3105
 URL: https://issues.apache.org/jira/browse/ISIS-3105
 Project: Isis
  Issue Type: New Feature
  Components: Isis Persistence JDO, Isis Persistence JPA
Reporter: Andi Huber
Assignee: Andi Huber
 Fix For: 2.0.0-M8


What I've found regarding zone/offset information support:
* MariaDB ... no
* PostgreSQL ... no
* MySQL ... no
* Microsoft SQL Server ... yes
* Oracle DB ... yes
* H2 ... yes

The sensible thing to do is to provide a custom type mapping for JDO and JPA in 
support of zone/offset temporals, by adding a secondary column that holds the 
zone/offset information. Similar to what we do with Blob/Clob.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3071) [Wicket Viewer] BootstrapFileInputField (FileUpload) is glitched

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-3071:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Wicket Viewer] BootstrapFileInputField (FileUpload) is glitched
> 
>
> Key: ISIS-3071
> URL: https://issues.apache.org/jira/browse/ISIS-3071
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Viewer Wicket
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
> Attachments: nested file upload.png
>
>
> File upload component from de.agilecoders.wicket.extensions, does not play 
> well with action prompts when there are multiple action parameters:
> Each time on changing dependent args adds a new (nested) upload component 
> inside the other.
> Can be reproduced via Demo->Prototyping->Generate Metamodel Diff, when adding 
> eg. namespaces within the dialog.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2968) [Validation] Guard against Members that contribute vetoed Domain-Types

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2968:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Validation] Guard against Members that contribute vetoed Domain-Types
> --
>
> Key: ISIS-2968
> URL: https://issues.apache.org/jira/browse/ISIS-2968
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Core
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> I'm currently not sure what happens if a vetoed type appears as a property-, 
> action-return- or action-parameter-type. That should trigger a MM validation 
> error, such that these types cannot find a sneaky way into the MM.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3051) [Validation] Fail early, if declared and mixed-in Actions share same Member-id.

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-3051:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Validation] Fail early, if declared and mixed-in Actions share same 
> Member-id.
> ---
>
> Key: ISIS-3051
> URL: https://issues.apache.org/jira/browse/ISIS-3051
> Project: Isis
>  Issue Type: Improvement
>  Components: Isis Viewer Wicket
>Affects Versions: 2.0.0-M8
>Reporter: Patrick Deenen
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> Update: 
> if a declared method and a mixed-in method share the same member-id, the 
> declared method takes precedence - we need to change that behavior and 
> instead fail early, with MM validation error, not allowing this sort of 
> method action overriding



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-3015) [Wicket Viewer] Property Edit via FormExecutorDefault, will not display Recoverable Exception

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-3015:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Wicket Viewer] Property Edit via FormExecutorDefault, will not display 
> Recoverable Exception
> -
>
> Key: ISIS-3015
> URL: https://issues.apache.org/jira/browse/ISIS-3015
> Project: Isis
>  Issue Type: Improvement
>  Components: Wicket Viewer
>Affects Versions: 2.0.0-M7
>Reporter: Miklós Győrfi
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> During property edit, FormExecutorDefault does not display database error, 
> because it checks 
> {code:java}
> !formExecutorContext.isWithinInlinePrompt(){code}
>  condition. 
> It would be nice if ExceptionRecognizerService/ExceptionRecognizer could mark 
> the exception in Recognition if:
>  * The exception should be displayed as message in Action/Property/Inline 
> edit.
>  * This feature default to configuration
> This protocol should be supported in FormExecutorDefault.
> Anyway, the current protocol does not work at all, it forwards the exception, 
> but does not display the error page neither due to the WebRequestCycleForIsis 
> and the JGrowlUtil bug. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2972) [Question] Server Side Pagination for Collections

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2972:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Question] Server Side Pagination for Collections
> -
>
> Key: ISIS-2972
> URL: https://issues.apache.org/jira/browse/ISIS-2972
> Project: Isis
>  Issue Type: New Feature
>  Components: Isis Core, Isis Viewer Wicket
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> Research question as of mailing-list
> https://lists.apache.org/thread/19dqmsd94ww5gzjcycqpzpjhn23ttnly 
> Can we do this?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2983) [Wicket Viewer] Infinite Loop with Visibility Advisors in Tables

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2983:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [Wicket Viewer] Infinite Loop with Visibility Advisors in Tables
> 
>
> Key: ISIS-2983
> URL: https://issues.apache.org/jira/browse/ISIS-2983
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Viewer Wicket
>Affects Versions: 2.0.0-M6
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> Reported by Martin Hesse:
> I just had a case where when all members of type A are hidden, then rendering 
> a collection of instances of type B that have a field of type A will result 
> in an endless loop (M6).
> ... but the problem went away when I explicitly vetoed visibility of the 
> member (field) of type A in type B



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2822) Wrapper: async executions must run within their own exclusive transaction

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2822:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> Wrapper: async executions must run within their own exclusive transaction
> -
>
> Key: ISIS-2822
> URL: https://issues.apache.org/jira/browse/ISIS-2822
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Core
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> Ideally to be enforced by running on a different (isolated) thread. 
> Yet we are using the fork-join common pool, which provides no such guarantee.
> Currently an async execution might eventually run on the same thread as the 
> caller, and hence participate in the same transaction as the caller. The 
> framework must prevent this from happening.



--
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.

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2959:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> [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-RC1
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2958) IsisToWicketTreeAdapter$TreeModel Deserialization fails to resolve Injection Points

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2958:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> IsisToWicketTreeAdapter$TreeModel Deserialization fails to resolve Injection 
> Points
> ---
>
> Key: ISIS-2958
> URL: https://issues.apache.org/jira/browse/ISIS-2958
> Project: Isis
>  Issue Type: Bug
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>
> {{org.apache.isis.viewer.wicket.ui.components.entity.icontitle.EntityIconAndTitlePanel.determineTitle()}}{color:#1d1c1d}
>  would try to resolve the title of the node and then fails with a 
> {color}{{NullPointerException}}
> Nodes are view models, not entities.
> Current workaround: inject the dependencies via custom TreeAdapter 
> implementation.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2805) Lifecycle events do not fire for JDO (either)

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2805:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> Lifecycle events do not fire for JDO (either)
> -
>
> Key: ISIS-2805
> URL: https://issues.apache.org/jira/browse/ISIS-2805
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Core, Isis Persistence JDO
>Affects Versions: 2.0.0-M5
>Reporter: Daniel Keir Haywood
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-RC1
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (ISIS-2683) BS3 Menu layout cssClassFa not honored

2022-08-02 Thread Andi Huber (Jira)


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

Andi Huber updated ISIS-2683:
-
Fix Version/s: 2.0.0-RC1
   (was: 2.0.0-M8)

> BS3 Menu layout cssClassFa not honored
> --
>
> Key: ISIS-2683
> URL: https://issues.apache.org/jira/browse/ISIS-2683
> Project: Isis
>  Issue Type: Bug
>  Components: Isis Viewer Wicket
>Affects Versions: 2.0.0-M5
>Reporter: Martin Hesse
>Assignee: Andi Huber
>Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> The cssClassFa attribute of the menu XML element in the menubar layout xml is 
> not pickep up and the specified icon not rendered in the menu wicket 
> component.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)