March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4870) Improve add-user handling to allow custom dictionary/keyboard

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4870?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4870: ------------------------------------- Issue Type: Feature Request (was: Enhancement) > Improve add-user handling to allow custom dictionary/keyboard > ------------------------------------------------------------- > > Key: WFCORE-4870 > URL: https://issues.redhat.com/browse/WFCORE-4870 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > > As is: > - default Keyboard is properties based setup, it is locked to default EN keyboard layout, properties file, that it reads are locked in management-domain jar > - default Dictionary is properties based setup, it is locked with few example word definitions, properties file, that it reads are locked in management-domain jar > - SimplePasswordStrengthChecker - default implementation of password check algorithm. Sadly with private fields, so it is not extendable( seems like oversight ) > - bin/add-user.properties - config file with properties that allow change how SimplePasswordStrengthChecker or other implementation behaves. It allows to load custom implementation of PasswordStrengthChecker > Ideally, user should be able to: > - configure layout/dictionary content > - configure implementation of keyboard/dictionary > - extend SimplePasswordStrengthChecker to change keyboard/dictionary, implement more checks. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4870) Improve add-user handling to allow custom dictionary/keyboard

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4870?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-4870: ------------------------------------------ PasswordStrengthChecker is an internal API, as is the module that contains it. It could not stay where it is and be an end user API. I'm not sure where it could go. It would probably have to be external to WildFly, which is quite a lot. This involves user configurable behavior so it is a Feature Request. > Improve add-user handling to allow custom dictionary/keyboard > ------------------------------------------------------------- > > Key: WFCORE-4870 > URL: https://issues.redhat.com/browse/WFCORE-4870 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > > As is: > - default Keyboard is properties based setup, it is locked to default EN keyboard layout, properties file, that it reads are locked in management-domain jar > - default Dictionary is properties based setup, it is locked with few example word definitions, properties file, that it reads are locked in management-domain jar > - SimplePasswordStrengthChecker - default implementation of password check algorithm. Sadly with private fields, so it is not extendable( seems like oversight ) > - bin/add-user.properties - config file with properties that allow change how SimplePasswordStrengthChecker or other implementation behaves. It allows to load custom implementation of PasswordStrengthChecker > Ideally, user should be able to: > - configure layout/dictionary content > - configure implementation of keyboard/dictionary > - extend SimplePasswordStrengthChecker to change keyboard/dictionary, implement more checks. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5056) [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned

by Roger Martinez (Jira)

[ https://issues.redhat.com/browse/DROOLS-5056?page=com.atlassian.jira.plug... ] Roger Martinez commented on DROOLS-5056: ---------------------------------------- [~manstis] I don't remember any recent fix on this, although I recently added [this commit|https://github.com/kiegroup/kie-wb-common/commit/a082270bdeaa87668...], which contains changes on the "drag proxies" and the command executed during drag operations... so maybe this commit has some implication here, but not really sure. > [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned > ------------------------------------------------------------------------------- > > Key: DROOLS-5056 > URL: https://issues.redhat.com/browse/DROOLS-5056 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: issue.mp4, taxRate.dmn > > > Sometimes the nodes inside the Decision Service are positioned outside from the Decision Service when the .DMN is saved an open again. > I was unable to map exact when this happen, but I noticed that this happens depending on the changes you do in the position and size of the Decision Service and its inner nodes. > I recorded a video with 2 minutes when the issue happens in the last seconds. > As it can be notice it takes lots of trials to reproduce the issue. > Also I was unable to reproduce the issue in the Business Central, so I'm not sure if it is related to DMN Editor in VS Code or DMN Editor itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13290) Observability TCKs fail when -Dtestsuite.default.build.project.prefix=ee- is used

by James Perkins (Jira)

James Perkins created WFLY-13290: ------------------------------------ Summary: Observability TCKs fail when -Dtestsuite.default.build.project.prefix=ee- is used Key: WFLY-13290 URL: https://issues.redhat.com/browse/WFLY-13290 Project: WildFly Issue Type: Bug Components: MP Config, MP Health, MP Metrics, MP OpenTracing, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 20.0.0.Beta1 Switching to using standalone-microprofile.xml as the default config file used by test servers when the MP TCKs run broke the -Dtestsuite.default.build.project.prefix=ee- test setup that was part of WFLY-12985. (See recent https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxAltDistJdk8 results.). This is because the config/health/metrics/opentracing tcks will run against a server based on the ee-build output if that property is set, and those server's don't provide standalone-microprofile.xml. Fix is to configure surefire/arquillian to use standalone.xml if that property is set. The clustering testsuite fails as well, because the CLI script used to set up clustering tries to modify a non-existent standalone-microprofile-ha.xml. Solution there is separate that modification out into a separate script and only run it when needed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13289) HttpSessionActivationListener not triggered for mutated attribute at the end of the request

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13289?page=com.atlassian.jira.plugi... ] Paul Ferraro closed WFLY-13289. ------------------------------- Resolution: Rejected Apparently, my past self outsmarted my present self. This is already handled via ImmutableSessionAttributeActivationNotifier.close(). > HttpSessionActivationListener not triggered for mutated attribute at the end of the request > ------------------------------------------------------------------------------------------- > > Key: WFLY-13289 > URL: https://issues.redhat.com/browse/WFLY-13289 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > This only affects ATTRIBUTE granularity when using a write-through cache store. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13289) HttpSessionActivationListener not triggered for mutated attribute at the end of the request

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13289: ----------------------------------- Summary: HttpSessionActivationListener not triggered for mutated attribute at the end of the request Key: WFLY-13289 URL: https://issues.redhat.com/browse/WFLY-13289 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 19.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro This only affects ATTRIBUTE granularity when using a write-through cache store. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-263) Logger Lookup is much slower as with JDK 8

by James Perkins (Jira)

[ https://issues.redhat.com/browse/LOGMGR-263?page=com.atlassian.jira.plugi... ] James Perkins commented on LOGMGR-263: -------------------------------------- WFCORE-4860 has been merged upstream which should help with this a bit if you do not use any per-logging deployments. A proper fix or workaround for the log manager is still needed. > Logger Lookup is much slower as with JDK 8 > ------------------------------------------ > > Key: LOGMGR-263 > URL: https://issues.redhat.com/browse/LOGMGR-263 > Project: JBoss Log Manager > Issue Type: Bug > Environment: WildFly 17, OpenJDK 11 > Reporter: Andreas Liebscher > Assignee: James Perkins > Priority: Critical > Attachments: ClassInEar.java, LogContextCacher.java, getlogger-stack.txt, grafik1570016303722 (1).png, grafik1570016303722.png, grafik1570016791285.png, logger-demo.war, responsetimes.png > > > During upgrading a Java EE application from WildFly 13 with JDK 8 to WildFly 17 with JDK 11 we had a serious performance issue. We identified the usage of the logging framework SLF4J with the pattern `Logger log = LoggerFactory.getLogger(XXX.class)` was the reason when a lot of calls to `getLogger` occur in parallel. As workaround we added `static` to some code hotspots to get back the performance we were used to. Also WildFly 13 with JDK 8 got a performance improvement with the added `static` keyword. > Please check the VisualVM output as prove of JDKSpecific got slower: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13288) Upgrade Mojarra to 2.3.9.SP08

by Farah Juma (Jira)

Farah Juma created WFLY-13288: --------------------------------- Summary: Upgrade Mojarra to 2.3.9.SP08 Key: WFLY-13288 URL: https://issues.redhat.com/browse/WFLY-13288 Project: WildFly Issue Type: Component Upgrade Components: JSF Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13287) Sync version of arquillian-testng-container with arquillian-junit-container

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13287?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13287: -------------------------------- Description: (was: This looks it will require updating the upstream MP OpenAPI TCK. {noformat} 2020-03-25 13:42:00,486 WARN [org.jboss.modules.define] (default task-1) Failed to define class org.jboss.arquillian.testng.Arquillian in Module "deployment.3aa1b9e0-8630-42cd-a9c8-2e523f4e8935.war" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link org/jboss/arquillian/testng/Arquillian (Module "deployment.3aa1b9e0-8630-42cd-a9c8-2e523f4e8935.war" from Service Module Loader): org/testng/IHookable {noformat}) > Sync version of arquillian-testng-container with arquillian-junit-container > --------------------------------------------------------------------------- > > Key: WFLY-13287 > URL: https://issues.redhat.com/browse/WFLY-13287 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenAPI, Test Suite > Affects Versions: 19.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13287) Sync version of arquillian-testng-container with arquillian-junit-container

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13287?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13287: -------------------------------- Description: This looks it will require updating the upstream MP OpenAPI TCK. {noformat} 2020-03-25 13:42:00,486 WARN [org.jboss.modules.define] (default task-1) Failed to define class org.jboss.arquillian.testng.Arquillian in Module "deployment.3aa1b9e0-8630-42cd-a9c8-2e523f4e8935.war" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link org/jboss/arquillian/testng/Arquillian (Module "deployment.3aa1b9e0-8630-42cd-a9c8-2e523f4e8935.war" from Service Module Loader): org/testng/IHookable {noformat} > Sync version of arquillian-testng-container with arquillian-junit-container > --------------------------------------------------------------------------- > > Key: WFLY-13287 > URL: https://issues.redhat.com/browse/WFLY-13287 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenAPI, Test Suite > Affects Versions: 19.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > This looks it will require updating the upstream MP OpenAPI TCK. > {noformat} > 2020-03-25 13:42:00,486 WARN [org.jboss.modules.define] (default task-1) Failed to define class org.jboss.arquillian.testng.Arquillian in Module "deployment.3aa1b9e0-8630-42cd-a9c8-2e523f4e8935.war" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link org/jboss/arquillian/testng/Arquillian (Module "deployment.3aa1b9e0-8630-42cd-a9c8-2e523f4e8935.war" from Service Module Loader): org/testng/IHookable > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 March 2020