November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4517) Contextual Menus after scrolling

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4517?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-4517: ------------------------------------- [~manstis] I have feeling this could be solved by AF-2347, am I right? > Contextual Menus after scrolling > -------------------------------- > > Key: DROOLS-4517 > URL: https://issues.jboss.org/browse/DROOLS-4517 > Project: Drools > Issue Type: Bug > Components: DMN Editor, Scenario Simulation and Testing > Affects Versions: 7.27.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-09-10 09-48-27.png, Screenshot from 2019-09-10 09-53-24.png > > > There is an issue with contextual menus in ScenarioSimalation and DMN designers. When user wants to show the contextual menu after scrolling was done: > h3. ScenarioSimulation > Menu is shown at inappropriate place > !Screenshot from 2019-09-10 09-48-27.png|thumbnail! > h3. DMN > Menu is not shown at all > !Screenshot from 2019-09-10 09-53-24.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1910) Develop JWT Token Issuer

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1910: ------------------------------------- Summary: Develop JWT Token Issuer Key: ELY-1910 URL: https://issues.jboss.org/browse/ELY-1910 Project: WildFly Elytron Issue Type: Feature Request Components: API / SPI Reporter: Darran Lofthouse Fix For: 2.0.0.Alpha6 Assigning to API / SPI for now but we may want to create a new component to track token based authentication, especially JWT. It may be desirable for us to be able to issue JWT tokens that can be used elsewhere. At the moment our identity propagation makes use of credentials delegated to us during authentication but we have some more opportunities if we can obtain new credentials dynamically for this propagation. An ideal use case for this could be a traditional web application already secured using traditional authentication such as username / password via a form, in that case the application will have a resulting SecurityIdentity with attributes, roles, and permissions assigned. This feature request is to consider a component internal to the process to convert the SecurityIdentity to a JWT token that can now be used for any outbound calls as the identity to propagate the identity. One possibility is some kind of transformation that can be applied on the SecurityDomain so the resulting SecurityIdentity has an associated JWT token credential as soon as it is created. Another alternative is more integration within authentication client, the destination could be taken into account so different tokens / mappings are applied for different destinations. I wont create the separate Jira issue yet but this could also open an option to dynamically obtain a token from a remote issuer - we may have been delegated a credential we can use to authentication against a remote identity provider and request a token that way. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2406) MERGE3 not working with TCP using ForkJoinPool

by Olivier Peyrusse (Jira)

Olivier Peyrusse created JGRP-2406: -------------------------------------- Summary: MERGE3 not working with TCP using ForkJoinPool Key: JGRP-2406 URL: https://issues.jboss.org/browse/JGRP-2406 Project: JGroups Issue Type: Bug Affects Versions: 4.1.8 Reporter: Olivier Peyrusse Assignee: Bela Ban Attachments: logs.tgz, project.zip, timeline.txt Using the TCP protocol with the ForkJoinPool is causing constant failures of MERGE3. I consistently observed the following, from the point of view of a member M - M asks for other coordinator views. It contacts A and B - A and B send their views - M waits and timeouts for receiving views and abort the merge - immediately after aborting the merge, M process messages containing the views of A and B. In [^timeline.txt], you will see the extracts for logs from the various members at play. After many experiments, the one parameter causing this issue is in the TCP protocol. {code:xml} <TCP ... thread_pool.use_fork_join_pool="true" /> {code} Setting {{thread_pool.use_fork_join_pool}} to true repeatedly produces the problem, while using {{thread_pool.use_fork_join_pool}} with false works fine. Project details: - as tested within Kubernetes, this project uses KUBE_PING as its discovery protocol - to understand the reason for the failed merges, I created the protocol MERGE4, that is MERGE3 with additional logs. - [^logs.tgz] contains all logs from the various members involved in the test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2406) MERGE3 not working with TCP using ForkJoinPool

by Olivier Peyrusse (Jira)

[ https://issues.jboss.org/browse/JGRP-2406?page=com.atlassian.jira.plugin.... ] Olivier Peyrusse updated JGRP-2406: ----------------------------------- Priority: Minor (was: Major) > MERGE3 not working with TCP using ForkJoinPool > ---------------------------------------------- > > Key: JGRP-2406 > URL: https://issues.jboss.org/browse/JGRP-2406 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.8 > Reporter: Olivier Peyrusse > Assignee: Bela Ban > Priority: Minor > Attachments: logs.tgz, project.zip, timeline.txt > > > Using the TCP protocol with the ForkJoinPool is causing constant failures of MERGE3. > I consistently observed the following, from the point of view of a member M > - M asks for other coordinator views. It contacts A and B > - A and B send their views > - M waits and timeouts for receiving views and abort the merge > - immediately after aborting the merge, M process messages containing the views of A and B. > In [^timeline.txt], you will see the extracts for logs from the various members at play. > After many experiments, the one parameter causing this issue is in the TCP protocol. > {code:xml} > <TCP > ... > thread_pool.use_fork_join_pool="true" /> > {code} > Setting {{thread_pool.use_fork_join_pool}} to true repeatedly produces the problem, while using {{thread_pool.use_fork_join_pool}} with false works fine. > Project details: > - as tested within Kubernetes, this project uses KUBE_PING as its discovery protocol > - to understand the reason for the failed merges, I created the protocol MERGE4, that is MERGE3 with additional logs. > - [^logs.tgz] contains all logs from the various members involved in the test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4116) JDK 10: illegal reflective access by ClassReflectionIndex

by Thorsten Möller (Jira)

[ https://issues.jboss.org/browse/WFCORE-4116?page=com.atlassian.jira.plugi... ] Thorsten Möller reopened WFCORE-4116: ------------------------------------- Using Wildfly 18.0.1 on JDK 11.0.5, I have noticed one more illegal reflective access: {code} WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/Users/thorsten/development/wildfly-18.0.1.Final/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.2.Final.jar!/) to method java.lang.Object.clone() WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release {code} Note that this access only occurs on deploying something - in my case a WAR is deployed. If the server is started such that nothing is deployed, there is no such error. > JDK 10: illegal reflective access by ClassReflectionIndex > --------------------------------------------------------- > > Key: WFCORE-4116 > URL: https://issues.jboss.org/browse/WFCORE-4116 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.Final, 6.0.2.Final, 7.0.0.Final > Reporter: Thorsten Möller > Assignee: James Perkins > Priority: Major > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > Using WF14 and Oracle JDK 10.0.2, there is an illegal reflective access warning while WF boots: > {code} > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.jboss.as.server.deployment.reflect.ClassReflectionIndex (jar:file:/Users/.../wildfly-14.0.0.Final/modules/system/layers/base/org/jboss/as/server/main/wildfly-server-6.0.1.Final.jar!/) to method java.lang.Object.finalize() > WARNING: Please consider reporting this to the maintainers of org.jboss.as.server.deployment.reflect.ClassReflectionIndex > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4791) [DMN Designer] Not able to edit by double click after scroll

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4791?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4791: ----------------------------------- Story Points: 5 Sprint: 2019 Week 47-49 (from Nov 18) > [DMN Designer] Not able to edit by double click after scroll > ------------------------------------------------------------ > > Key: DROOLS-4791 > URL: https://issues.jboss.org/browse/DROOLS-4791 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: aTable.dmn, edit-cell.webm > > > User is not able to invoke cell edito mode if he scrolled the dmn grid before. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4792) [DMN Designer] Eliminate producing of RenedringInformation - BaseKeyboardOperation

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4792?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4792: -------------------------------- Description: During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. According the changes related to the comment above, we should update also the [BaseKeyboardOperation#scrollSelectedCellIntoView|https://github.com/kiegr...]. This method can be rewritten to produce {{RenderingInformation}} just once. was: During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. According the changes related to the comment above, we should update also the [BaseKeyboardOperation#scrollSelectedCellIntoView|https://github.com/kiegr...]. This method can be rewritten to produce `RenderingInformation` just once. > [DMN Designer] Eliminate producing of RenedringInformation - BaseKeyboardOperation > ---------------------------------------------------------------------------------- > > Key: DROOLS-4792 > URL: https://issues.jboss.org/browse/DROOLS-4792 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. > According the changes related to the comment above, we should update also the [BaseKeyboardOperation#scrollSelectedCellIntoView|https://github.com/kiegr...]. This method can be rewritten to produce {{RenderingInformation}} just once. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4793) [DMN Designer] Eliminate producing of RenedringInformation - BaseCellSelectionManager

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4793?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4793: -------------------------------- Description: During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. According the changes related to the comment above, we should update also the [BaseCellSelectionManager#startEditingCell|https://github.com/kiegroup/app...]. This method can be rewritten to produce {{RenderingInformation}} just once. was: During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. According the changes related to the comment above, we should update also the [BaseCellSelectionManager#startEditingCell|https://github.com/kiegroup/app...]. This method can be rewritten to produce `RenderingInformation` just once. > [DMN Designer] Eliminate producing of RenedringInformation - BaseCellSelectionManager > ------------------------------------------------------------------------------------- > > Key: DROOLS-4793 > URL: https://issues.jboss.org/browse/DROOLS-4793 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. > According the changes related to the comment above, we should update also the [BaseCellSelectionManager#startEditingCell|https://github.com/kiegroup/app...]. This method can be rewritten to produce {{RenderingInformation}} just once. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4792) [DMN Designer] Eliminate producing of RenedringInformation - BaseKeyboardOperation

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4792?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4792: -------------------------------- Description: During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. According the changes related to the comment above, we should update also the [BaseKeyboardOperation#scrollSelectedCellIntoView|https://github.com/kiegr...]. This method can be rewritten to produce `RenderingInformation` just once. was: During the DROOLS-4735 development, it was found out repetitive producing of `RenderingInformation` decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. According the changes related to the comment above, we should update also the [BaseKeyboardOperation#scrollSelectedCellIntoView|https://github.com/kiegr...]. This method can be rewritten to produce `RenderingInformation` just once. > [DMN Designer] Eliminate producing of RenedringInformation - BaseKeyboardOperation > ---------------------------------------------------------------------------------- > > Key: DROOLS-4792 > URL: https://issues.jboss.org/browse/DROOLS-4792 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. > According the changes related to the comment above, we should update also the [BaseKeyboardOperation#scrollSelectedCellIntoView|https://github.com/kiegr...]. This method can be rewritten to produce `RenderingInformation` just once. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4793) [DMN Designer] Eliminate producing of RenedringInformation - BaseCellSelectionManager

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4793?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4793: -------------------------------- Description: During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. According the changes related to the comment above, we should update also the [BaseCellSelectionManager#startEditingCell|https://github.com/kiegroup/app...]. This method can be rewritten to produce `RenderingInformation` just once. was: During the DROOLS-4735 development, it was found out repetitive producing of `RenderingInformation` decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. According the changes related to the comment above, we should update also the [BaseKeyboardOperation#scrollSelectedCellIntoView|https://github.com/kiegr...]. This method can be rewritten to produce `RenderingInformation` just once. > [DMN Designer] Eliminate producing of RenedringInformation - BaseCellSelectionManager > ------------------------------------------------------------------------------------- > > Key: DROOLS-4793 > URL: https://issues.jboss.org/browse/DROOLS-4793 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. > According the changes related to the comment above, we should update also the [BaseCellSelectionManager#startEditingCell|https://github.com/kiegroup/app...]. This method can be rewritten to produce `RenderingInformation` just once. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2019