January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4972: ------------------------------------ [~uxdlc] I think I can easily handle most of these requirements in this ticket. I'll keep you updated. > Buttons stay disabled when switching to textual collection editor > ----------------------------------------------------------------- > > Key: DROOLS-4972 > URL: https://issues.redhat.com/browse/DROOLS-4972 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm > > > If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2441) Changes to MembershipListener, StateListener, MessageListener

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2441?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2441. ---------------------------- Resolution: Done > Changes to MembershipListener,StateListener,MessageListener > ----------------------------------------------------------- > > Key: JGRP-2441 > URL: https://issues.redhat.com/browse/JGRP-2441 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0 > > > Investigate > * Why is MessageListener still needed? Can't we just use {{Receiver}}? > * Why does {{MessageListener}} subclass {{StateListener}}? > * Are callbacks {{block()}}, {{unblock()}} and {{suspect()}} still needed? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-12093?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-12093: ------------------------------------- Hi [~emmartins] [~svkreml], As per my understanding end time should not be update, after clicking on Update list button. And also please let me if you are working on this issue? Thanks, Parul Sharma > bug in tutorial "batch-processing" with column "End Time" > --------------------------------------------------------- > > Key: WFLY-12093 > URL: https://issues.redhat.com/browse/WFLY-12093 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Environment: batch-processing > Reporter: Святослав Кремлёв > Assignee: Eduardo Martins > Priority: Major > Attachments: 2019-05-18 23_16_51-Batch Processing.png > > > in file > org/jboss/as/quickstarts/batch/controller/JobData.java > {code} > public Date getEndTime() { > endTime = new Date(); > return endTime.getTime() == 0 ? null : endTime; > } > {code} > its returns current time every time, not the job endTime -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13027) Missing reference to openapi layer in Galleon layers page in Admin Guide

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13027?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-13027: --------------------------------------- Assignee: Brian Stansberry (was: Paul Ferraro) > Missing reference to openapi layer in Galleon layers page in Admin Guide > ------------------------------------------------------------------------ > > Key: WFLY-13027 > URL: https://issues.redhat.com/browse/WFLY-13027 > Project: WildFly > Issue Type: Bug > Components: MP OpenAPI > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 19.0.0.Beta2 > > > https://github.com/wildfly/wildfly/blob/master/docs/src/main/asciidoc/_ad... does not mention OpenAPI. > Apologies if it somehow got deleted as I have a vague memory of seeing it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4990) NullPointerException with executable model using accumulate max with null Date field

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4990?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4990: -------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > NullPointerException with executable model using accumulate max with null Date field > ------------------------------------------------------------------------------------ > > Key: DROOLS-4990 > URL: https://issues.redhat.com/browse/DROOLS-4990 > Project: Drools > Issue Type: Bug > Components: core engine, executable model > Affects Versions: 7.32.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > Labels: support > > Executing a rule containing accumulate max, eg: > {code} > rule AccumulateMaxDate > when > $max1 : Number() from accumulate( > StockTick(isSetDueDate == true > ,$time : dueDate); > max($time.getTime().getTime())) > then > end > {code} > fails with a NPE at runtime if the StockDate.dueDate field is null: > {noformat} > Caused by: java.lang.NullPointerException > at defaultpkg.RulesA0DFC3D10EA29F3818B87E11918D8020RuleMethods0.lambda$rule_AccumulateMaxDate$c9e019d8$1(RulesA0DFC3D10EA29F3818B87E11918D8020RuleMethods0.java:34) > at org.drools.model.functions.Function1$Impl.apply(Function1.java:35) > at org.drools.model.view.BindViewItem1.eval(BindViewItem1.java:85) > at org.drools.modelcompiler.constraints.BindingEvaluator.evaluate(BindingEvaluator.java:39) > at org.drools.modelcompiler.constraints.BindingEvaluator.evaluate(BindingEvaluator.java:35) > at org.drools.modelcompiler.constraints.LambdaAccumulator$BindingAcc.getAccumulatedObject(LambdaAccumulator.java:154) > at org.drools.modelcompiler.constraints.LambdaAccumulator.accumulate(LambdaAccumulator.java:88) > at org.drools.core.rule.SingleAccumulate.accumulate(SingleAccumulate.java:97) > ... 53 more > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4829) An operation to add a pattern-formatter resource does not correctly marshal the XML configuration

by James Perkins (Jira)

James Perkins created WFCORE-4829: ------------------------------------- Summary: An operation to add a pattern-formatter resource does not correctly marshal the XML configuration Key: WFCORE-4829 URL: https://issues.redhat.com/browse/WFCORE-4829 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Using an operation like {{/subsystem=logging/pattern-formatter=formatter:add}} will correctly add the formatter to the model. However after a reload an exception is logged as the default values are not marshalled into the XML. Along with this even if the element is marshalled, the {{pattern}} attribute seems to get set to "undefined" in the logging configuration which just logs the "undefined" for every log message. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13042) Jaeger tracer sender-binding isn't configurable

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13042?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13042: ------------------------------------ Fix Version/s: 19.0.0.Beta2 > Jaeger tracer sender-binding isn't configurable > ----------------------------------------------- > > Key: WFLY-13042 > URL: https://issues.redhat.com/browse/WFLY-13042 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 19.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > Fix For: 19.0.0.Beta2 > > > When configuring a jaeger tracer sender-binding parameter the server will no longer boot because of a NullPointerException in JaegerTracerConfiguration thus failing the boot of the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13043) ManagedScheduledExecutorService keeps executing tasks after an exception is thrown

by Vinicius Kopcheski (Jira)

Vinicius Kopcheski created WFLY-13043: ----------------------------------------- Summary: ManagedScheduledExecutorService keeps executing tasks after an exception is thrown Key: WFLY-13043 URL: https://issues.redhat.com/browse/WFLY-13043 Project: WildFly Issue Type: Bug Components: Concurrency Utilities Affects Versions: 18.0.1.Final Reporter: Vinicius Kopcheski Assignee: Eduardo Martins There is apparently a bug in the implementation of the ManagedScheduledExecutorService, more specifically when using the inherited method of the ScheduledExecutorService, [scheduleWithFixedDelay|https://docs.oracle.com/javase/7/docs/api/java/uti...]. On its javadoc it is stated "If any execution of the task encounters an exception, subsequent executions are suppressed.". When [this code|https://github.com/kopcheski/managed-scheduled-executor/blob/master/...] is executed in any Wildfly from 10 to 18, the task is kept alive in the scheduler after an exception is thrown and subsequent calls will happen anyway, contradicting the javadoc. To add evidences of a misbehavior, I did two extra checks: 1. Running the exact same code in another JavaEE server (Payara); 2. Using plain JavaSE with the ScheduledExecutorService. In both cases, after an exception being thrown, subsequent executions of it are - as the javadoc states - suppressed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4990) NullPointerException with executable model using accumulate max with null Date field

by Martin Weiler (Jira)

[ https://issues.redhat.com/browse/DROOLS-4990?page=com.atlassian.jira.plug... ] Martin Weiler moved RHDM-1216 to DROOLS-4990: --------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-4990 (was: RHDM-1216) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: core engine executable model (was: BRE) Affects Version/s: 7.32.0.Final (was: 7.6.0.GA) QE Status: NEW > NullPointerException with executable model using accumulate max with null Date field > ------------------------------------------------------------------------------------ > > Key: DROOLS-4990 > URL: https://issues.redhat.com/browse/DROOLS-4990 > Project: Drools > Issue Type: Bug > Components: core engine, executable model > Affects Versions: 7.32.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > Labels: support > > Executing a rule containing accumulate max, eg: > {code} > rule AccumulateMaxDate > when > $max1 : Number() from accumulate( > StockTick(isSetDueDate == true > ,$time : dueDate); > max($time.getTime().getTime())) > then > end > {code} > fails with a NPE at runtime if the StockDate.dueDate field is null: > {noformat} > Caused by: java.lang.NullPointerException > at defaultpkg.RulesA0DFC3D10EA29F3818B87E11918D8020RuleMethods0.lambda$rule_AccumulateMaxDate$c9e019d8$1(RulesA0DFC3D10EA29F3818B87E11918D8020RuleMethods0.java:34) > at org.drools.model.functions.Function1$Impl.apply(Function1.java:35) > at org.drools.model.view.BindViewItem1.eval(BindViewItem1.java:85) > at org.drools.modelcompiler.constraints.BindingEvaluator.evaluate(BindingEvaluator.java:39) > at org.drools.modelcompiler.constraints.BindingEvaluator.evaluate(BindingEvaluator.java:35) > at org.drools.modelcompiler.constraints.LambdaAccumulator$BindingAcc.getAccumulatedObject(LambdaAccumulator.java:154) > at org.drools.modelcompiler.constraints.LambdaAccumulator.accumulate(LambdaAccumulator.java:88) > at org.drools.core.rule.SingleAccumulate.accumulate(SingleAccumulate.java:97) > ... 53 more > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ] Elizabeth Clayton edited comment on DROOLS-4972 at 1/30/20 1:33 PM: -------------------------------------------------------------------- [~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to: - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list. - Consider renaming the action to "Add list value" or whatever most closely describes the action. - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, but the "Add new item" looks about right. !Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail! - Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo. Thanks! Liz was (Author: uxdlc): [~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to: - When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list. - Consider renaming the action to "Add list value" or whatever most closely describes the action. - Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, while the "Add new item" looks about right. !Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail! - Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo. Thanks! Liz > Buttons stay disabled when switching to textual collection editor > ----------------------------------------------------------------- > > Key: DROOLS-4972 > URL: https://issues.redhat.com/browse/DROOLS-4972 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm > > > If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2020