January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1735) Clean up the 'wildfly-elytron-auth-server' module as it currently contains both public and private API

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1735?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1735: --------------------------------------- Need to try moving all private classes to a different module this module depends on and work through remaining issues. Identify any private classes that may have leaked into public API. > Clean up the 'wildfly-elytron-auth-server' module as it currently contains both public and private API > ------------------------------------------------------------------------------------------------------ > > Key: ELY-1735 > URL: https://issues.jboss.org/browse/ELY-1735 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha1, 1.9.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3548) Thread used by LoadBalancer remains when connection to kie-server fails during instantinating of KieServicesClient

by Maciej Swiderski (Jira)

[ https://issues.jboss.org/browse/DROOLS-3548?page=com.atlassian.jira.plugi... ] Maciej Swiderski updated DROOLS-3548: ------------------------------------- Sprint: 2019 Week 05-07 > Thread used by LoadBalancer remains when connection to kie-server fails during instantinating of KieServicesClient > ------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-3548 > URL: https://issues.jboss.org/browse/DROOLS-3548 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.11.0.Final, 7.14.0.Final > Environment: - Red Hat Decision Manager > - 7 > - Red Hat Process Automation Manager > - 7 > Reporter: Hiroko Miura > Assignee: Maciej Swiderski > Priority: Major > Labels: support > Attachments: rules-client.zip > > > When KieServicesClient fails to connect to KieServer, LoadBalancer is invoked to check availability of server like the following. > ~~~ > [2019/01/24 18:19:38.411] [pool-1-thread-1] [DEBUG] (LoadBalancer.java:149) - Starting to scan if any of the failed endpoints is back online > org.kie.server.common.rest.NoEndpointFoundException: No available endpoints found > at org.kie.server.client.balancer.impl.AbstractBalancerStrategy.checkEmpty(AbstractBalancerStrategy.java:27) > at org.kie.server.client.balancer.impl.RoundRobinBalancerStrategy.next(RoundRobinBalancerStrategy.java:37) > at org.kie.server.client.balancer.LoadBalancer.getUrl(LoadBalancer.java:52) > at org.kie.server.client.impl.AbstractKieServicesClientImpl.invoke(AbstractKieServicesClientImpl.java:809) > at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpGetRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:177) > at org.kie.server.client.impl.KieServicesClientImpl.getServerInfo(KieServicesClientImpl.java:159) > at org.kie.server.client.impl.KieServicesClientImpl.getCapabilitiesFromServer(KieServicesClientImpl.java:132) > at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:87) > at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:74) > at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101) > at com.sample.rules.test.KieServerRestClientTest.connectionFailureTest(KieServerRestClientTest.java:55) > ~~~ > But after that, the thread used by LoadBalancer remains until termination of client application as LoadBalancer.close() is not called. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1734) Clean up the 'wildfly-elytron-asn1' module as it currently contains both public and private API

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1734?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1734: --------------------------------------- Eliminate 'util' package by moving two utility classes up one level. properties file to remain private. Can eliminate _private messages by moving and making package private. > Clean up the 'wildfly-elytron-asn1' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------- > > Key: ELY-1734 > URL: https://issues.jboss.org/browse/ELY-1734 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha1, 1.9.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1734) Clean up the 'wildfly-elytron-asn1' module as it currently contains both public and private API

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1734?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1734: ---------------------------------- Comment: was deleted (was: Class OidsUtil needs to split into it's own module - no backwards compatibility required. ) > Clean up the 'wildfly-elytron-asn1' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------- > > Key: ELY-1734 > URL: https://issues.jboss.org/browse/ELY-1734 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha1, 1.9.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1734) Clean up the 'wildfly-elytron-asn1' module as it currently contains both public and private API

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1734?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1734: --------------------------------------- Class OidsUtil needs to split into it's own module - no backwards compatibility required. > Clean up the 'wildfly-elytron-asn1' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------- > > Key: ELY-1734 > URL: https://issues.jboss.org/browse/ELY-1734 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha1, 1.9.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2948) [DMN Designer] Change of selected data structure

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2948?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2948: -------------------------------- Description: When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. h2. Manual acceptance test - Steps to reproduce fixed. (/) - Check removed item definition is not present in output data-type select box. -- Was selected as output data type (x) -- Was selected as output data type of other node (/) -- Was not selected as output data-type (/) - Check added *top level* item definition *is present* in output data type select box (/) - Check added *nested level* item definition *is not present* in output data type select box (/) was: When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. h2. Manual acceptance test - Steps to reproduce fixed. (/) - Check removed item definition is not present in output data-type select box. -- Was selected as output data type (x) -- Was selected as output data type of other node -- Was not selected as output data-type - Check added *top level* item definition *is present* in output data type select box (/) - Check added *nested level* item definition *is not present* in output data type select box (/) > [DMN Designer] Change of selected data structure > ------------------------------------------------ > > Key: DROOLS-2948 > URL: https://issues.jboss.org/browse/DROOLS-2948 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: Port Clearance Rules - Solution 3.dmn > > > When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. > h2. Manual acceptance test > - Steps to reproduce fixed. (/) > - Check removed item definition is not present in output data-type select box. > -- Was selected as output data type (x) > -- Was selected as output data type of other node (/) > -- Was not selected as output data-type (/) > - Check added *top level* item definition *is present* in output data type select box (/) > - Check added *nested level* item definition *is not present* in output data type select box (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2948) [DMN Designer] Change of selected data structure

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2948?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2948: -------------------------------- Description: When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. h2. Manual acceptance test - Steps to reproduce fixed. (/) - Check removed item definition is not present in output data-type select box. -- Was selected as output data type (x) -- Was selected as output data type of other node -- Was not selected as output data-type - Check added *top level* item definition *is present* in output data type select box (/) - Check added *nested level* item definition *is not present* in output data type select box (/) was: When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. h2. Manual acceptance test - Steps to reproduce fixed. (/) - Check removed item definition is not present in output data-type select box. -- Was selected as output data type -- Was selected as output data type of other node -- Was not selected as output data-type - Check added *top level* item definition *is present* in output data type select box (/) - Check added *nested level* item definition *is not present* in output data type select box (/) > [DMN Designer] Change of selected data structure > ------------------------------------------------ > > Key: DROOLS-2948 > URL: https://issues.jboss.org/browse/DROOLS-2948 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: Port Clearance Rules - Solution 3.dmn > > > When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. > h2. Manual acceptance test > - Steps to reproduce fixed. (/) > - Check removed item definition is not present in output data-type select box. > -- Was selected as output data type (x) > -- Was selected as output data type of other node > -- Was not selected as output data-type > - Check added *top level* item definition *is present* in output data type select box (/) > - Check added *nested level* item definition *is not present* in output data type select box (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2948) [DMN Designer] Change of selected data structure

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2948?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2948: -------------------------------- Description: When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. h2. Manual acceptance test - Steps to reproduce fixed. (/) - Check removed item definition is not present in output data-type select box. -- Was selected as output data type -- Was selected as output data type of other node -- Was not selected as output data-type - Check added *top level* item definition *is present* in output data type select box (/) - Check added *nested level* item definition *is not present* in output data type select box (/) was: When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. h2. Manual acceptance test - Steps to reproduce fixed. (/) - Check removed item definition is not present in output data-type select box. -- Was selected as output data type -- Was selected as output data type of other node -- Was not selected as output data-type - Check added *top level* item definition *is present* in output data type select box - Check added *nested level* item definition *is not present* in output data type select box > [DMN Designer] Change of selected data structure > ------------------------------------------------ > > Key: DROOLS-2948 > URL: https://issues.jboss.org/browse/DROOLS-2948 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: Port Clearance Rules - Solution 3.dmn > > > When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. > h2. Manual acceptance test > - Steps to reproduce fixed. (/) > - Check removed item definition is not present in output data-type select box. > -- Was selected as output data type > -- Was selected as output data type of other node > -- Was not selected as output data-type > - Check added *top level* item definition *is present* in output data type select box (/) > - Check added *nested level* item definition *is not present* in output data type select box (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2948) [DMN Designer] Change of selected data structure

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2948?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2948: -------------------------------- Description: When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. h2. Manual acceptance test - Steps to reproduce fixed. (/) - Check removed item definition is not present in output data-type select box. -- Was selected as output data type -- Was selected as output data type of other node -- Was not selected as output data-type - Check added *top level* item definition *is present* in output data type select box - Check added *nested level* item definition *is not present* in output data type select box was: When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. h2. Manual acceptance test - Steps to reproduce fixed. - Check removed item definition is not present in output data-type select box. -- Was selected as output data type -- Was selected as output data type of other node -- Was not selected as output data-type - Check added *top level* item definition *is present* in output data type select box - Check added *nested level* item definition *is not present* in output data type select box > [DMN Designer] Change of selected data structure > ------------------------------------------------ > > Key: DROOLS-2948 > URL: https://issues.jboss.org/browse/DROOLS-2948 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: Port Clearance Rules - Solution 3.dmn > > > When user changes the currently selected data type, this change is not propagated into properties panel. User has to reopen the properties panel or reselect the element to load changes. > h2. Manual acceptance test > - Steps to reproduce fixed. (/) > - Check removed item definition is not present in output data-type select box. > -- Was selected as output data type > -- Was selected as output data type of other node > -- Was not selected as output data-type > - Check added *top level* item definition *is present* in output data type select box > - Check added *nested level* item definition *is not present* in output data type select box -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1807) Verification & Validation: Add three states for running the validation

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1807?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1807: --------------------------------- Sprint: (was: 2019 Week 02-04) > Verification & Validation: Add three states for running the validation > ----------------------------------------------------------------------- > > Key: DROOLS-1807 > URL: https://issues.jboss.org/browse/DROOLS-1807 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Anton Giertli > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools, verifier > > The statuses would be managed with system properties and extend the current on/off switch we have. > It will be possible to change the status for each validation check type. Check types are for example redundancy, range, missing columns. > > * Reactive > The "normal way" you make a change and the verification runs instantly > * Off > Verification is disabled > * On demand > Verification only runs when requested. Can be useful for large dtables where you for example change every value in a column and just really care about the verification status after all the changes. > Few ideas to think about: > # Might be worth it to also store the state per dtable. > # If V&V runs for over X amount of seconds. Ask if the user wants to change the setting from "Reactive" to "On Demand" for this table. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 January 2019