March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3420?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3420: --------------------------------- Sprint: (was: 2019 Week 11-13) > Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget > ------------------------------------------------------------------- > > Key: DROOLS-3420 > URL: https://issues.jboss.org/browse/DROOLS-3420 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Daniele Zonca > Priority: Minor > > SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget". > Later, ask [~Rikkola] to move it on upper framework. > *ADDITIONAL IMPROVEMENTS:* > # -When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list.- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047]. > # Change *Choose DMN asset* to *Choose a DMN asset*. > # The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down). > # -The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty.- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047]. > # -The field *Choose DMN asset* should be marked with *{color:red}*{color}* (required field).- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-644) Move relevant pages from mojo and to Confluence

by Filip Brychta (Jira)

Filip Brychta created SWSQE-644: ----------------------------------- Summary: Move relevant pages from mojo and to Confluence Key: SWSQE-644 URL: https://issues.jboss.org/browse/SWSQE-644 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta We have new space at confluence for OpenShift Service Mesh: https://docs.engineering.redhat.com/display/OSSM/OpenShift+Service+Mesh+Home We should move relevant content from * https://mojo.redhat.com/groups/jboss-operations-network-qe/content * https://docs.jboss.org/display/SWSQE/Kiali+QE -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3778) Receiving error InvocationTargetException on jdk11

by Yevgeniy Fomin (Jira)

[ https://issues.jboss.org/browse/DROOLS-3778?page=com.atlassian.jira.plugi... ] Yevgeniy Fomin updated DROOLS-3778: ----------------------------------- Attachment: Error log powermock.txt > Receiving error InvocationTargetException on jdk11 > -------------------------------------------------- > > Key: DROOLS-3778 > URL: https://issues.jboss.org/browse/DROOLS-3778 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.20.0.Final > Environment: * jdk11 > * Apache Maven 3.5.4 (Red Hat 3.5.4-4) > Reporter: Yevgeniy Fomin > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools, jdk11 > Attachments: Error log powermock.txt > > > There is InvocationTargetException on test classes if they are run on jdk11. The tests can be found in [module|https://github.com/kiegroup/kie-wb-common/tree/master/kie-wb-commo...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3778) Receiving error InvocationTargetException on jdk11

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3778?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3778: ------------------------------------- [~jfomin] please attach the txt file with the stacktrace. > Receiving error InvocationTargetException on jdk11 > -------------------------------------------------- > > Key: DROOLS-3778 > URL: https://issues.jboss.org/browse/DROOLS-3778 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.20.0.Final > Environment: * jdk11 > * Apache Maven 3.5.4 (Red Hat 3.5.4-4) > Reporter: Yevgeniy Fomin > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools, jdk11 > > There is InvocationTargetException on test classes if they are run on jdk11. The tests can be found in [module|https://github.com/kiegroup/kie-wb-common/tree/master/kie-wb-commo...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3778) Receiving error InvocationTargetException on jdk 11

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3778?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3778: -------------------------------- Summary: Receiving error InvocationTargetException on jdk 11 (was: Receiving error InvocationTargetException) > Receiving error InvocationTargetException on jdk 11 > --------------------------------------------------- > > Key: DROOLS-3778 > URL: https://issues.jboss.org/browse/DROOLS-3778 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.20.0.Final > Environment: * jdk11 > * Apache Maven 3.5.4 (Red Hat 3.5.4-4) > Reporter: Yevgeniy Fomin > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools, jdk11 > > There is InvocationTargetException on test classes if they are run on jdk11. The tests can be found in [module|https://github.com/kiegroup/kie-wb-common/tree/master/kie-wb-commo...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3778) Receiving error InvocationTargetException on jdk11

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3778?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3778: -------------------------------- Summary: Receiving error InvocationTargetException on jdk11 (was: Receiving error InvocationTargetException on jdk 11) > Receiving error InvocationTargetException on jdk11 > -------------------------------------------------- > > Key: DROOLS-3778 > URL: https://issues.jboss.org/browse/DROOLS-3778 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.20.0.Final > Environment: * jdk11 > * Apache Maven 3.5.4 (Red Hat 3.5.4-4) > Reporter: Yevgeniy Fomin > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools, jdk11 > > There is InvocationTargetException on test classes if they are run on jdk11. The tests can be found in [module|https://github.com/kiegroup/kie-wb-common/tree/master/kie-wb-commo...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3778) Receiving error InvocationTargetException

by Yevgeniy Fomin (Jira)

Yevgeniy Fomin created DROOLS-3778: -------------------------------------- Summary: Receiving error InvocationTargetException Key: DROOLS-3778 URL: https://issues.jboss.org/browse/DROOLS-3778 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.20.0.Final Environment: * jdk11 * Apache Maven 3.5.4 (Red Hat 3.5.4-4) Reporter: Yevgeniy Fomin Assignee: Michael Anstis There is InvocationTargetException on test classes if they are run on jdk11. The tests can be found in [module|https://github.com/kiegroup/kie-wb-common/tree/master/kie-wb-commo...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3774) Add auditing functionality to record/log which rules fired during a specific run

by Duncan Doyle (Jira)

[ https://issues.jboss.org/browse/DROOLS-3774?page=com.atlassian.jira.plugi... ] Duncan Doyle commented on DROOLS-3774: -------------------------------------- Some additional context: This is what other engines/vendors provides through their BI tool, that then enables to either store it (for traceability / audit ability reasons) and/ or send it as a letter to end-customers - eg 'Your mortgage application was rejected because of reason XYZ' where reason XYZ is rule XYZ >From a business perspective; how many mortgage applications are we rejecting because of reason XYZ, should we change those (are the rules too tight, too loose ...) >> eg can we increase risk to get more business? or do we need to offer a new banking product? > Add auditing functionality to record/log which rules fired during a specific run > -------------------------------------------------------------------------------- > > Key: DROOLS-3774 > URL: https://issues.jboss.org/browse/DROOLS-3774 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.19.0.Final > Reporter: Duncan Doyle > Assignee: Mario Fusco > Priority: Major > > We've had multiple requests to add an ootb auditing/logging feature to Drools. The basic requirements is to allow users to audit which rules fired against which data and for what reason. > For example, when you want to determine a fraud transaction, and you insert transactions into an engine, you want to know why a transaction was marked as fraudulent. So you want to know which rules fired against which transaction. > Another requirement I've seen is the following: > [quote] > Furthermore, they want the dashboard to show all the rules that execute by task stage in summary and then have the ability to drill into that list to see the individual delinquent account and the rules fired against it. > [/quote] > I know that we can add listeners to the engine to record things like MatchFired, but it would be great if we would have an ootb feature for this. Maybe even an API that instead of returning the number of rules fired, would be able to return the entire execution context. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11869) JSF Session / View Beans @Destroy not invoked after GC

by Teresa Miyar (Jira)

[ https://issues.jboss.org/browse/WFLY-11869?page=com.atlassian.jira.plugin... ] Teresa Miyar updated WFLY-11869: -------------------------------- Summary: JSF Session / View Beans @Destroy not invoked after GC (was: [GSS](7.2.z) JSF Session / View Beans @Destroy not invoked after GC) > JSF Session / View Beans @Destroy not invoked after GC > ------------------------------------------------------ > > Key: WFLY-11869 > URL: https://issues.jboss.org/browse/WFLY-11869 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 16.0.0.Final > Reporter: Teresa Miyar > Assignee: Teresa Miyar > Priority: Major > Attachments: dumpWithFix.hprof.zip, dumpWithProblem.hprof.zip, reproducers.zip > > > JSF Session / View Beans @Destroy not invoked after GC > This commit to fix a JSF memory leak appears to be related: > https://github.com/wildfly/wildfly/commit/6b28dd31e4fe40addebbb975f70dc10... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11869) [GSS](7.2.z) JSF Session / View Beans @Destroy not invoked after GC

by Teresa Miyar (Jira)

[ https://issues.jboss.org/browse/WFLY-11869?page=com.atlassian.jira.plugin... ] Teresa Miyar moved JBEAP-16574 to WFLY-11869: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11869 (was: JBEAP-16574) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JSF (was: JSF) Affects Version/s: 16.0.0.Final (was: 7.2.0.GA) Fix Version/s: (was: 7.2.2.GA) > [GSS](7.2.z) JSF Session / View Beans @Destroy not invoked after GC > ------------------------------------------------------------------- > > Key: WFLY-11869 > URL: https://issues.jboss.org/browse/WFLY-11869 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 16.0.0.Final > Reporter: Teresa Miyar > Assignee: Teresa Miyar > Priority: Major > Attachments: dumpWithFix.hprof.zip, dumpWithProblem.hprof.zip, reproducers.zip > > > JSF Session / View Beans @Destroy not invoked after GC > This commit to fix a JSF memory leak appears to be related: > https://github.com/wildfly/wildfly/commit/6b28dd31e4fe40addebbb975f70dc10... -- 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 March 2019