February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5002) [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5002?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5002: -------------------------------- Priority: Minor (was: Major) > [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field > ---------------------------------------------------------------------------------- > > Key: DROOLS-5002 > URL: https://issues.redhat.com/browse/DROOLS-5002 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2020-02-04 07-50-43.png, Screenshot from 2020-02-04 07-50-53.png > > > Show a visual indication of the current drag level. See (the blue line): > !image-2019-08-27-12-40-51-854.png|width=500! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5002) [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5002?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5002: -------------------------------- Issue Type: Bug (was: Task) > [DMN Designer] Data Types - Nested Structure is expanded when adding sibling field > ---------------------------------------------------------------------------------- > > Key: DROOLS-5002 > URL: https://issues.redhat.com/browse/DROOLS-5002 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-02-04 07-50-43.png, Screenshot from 2020-02-04 07-50-53.png > > > Show a visual indication of the current drag level. See (the blue line): > !image-2019-08-27-12-40-51-854.png|width=500! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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: ------------------------------------- [~cfang] Thanks > 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: Parul Sharma > 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)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4831) CLI boot, exception not thrown when error printed to error file

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4831?page=com.atlassian.jira.plug... ] Jean Francois Denise updated WFCORE-4831: ----------------------------------------- Fix Version/s: 11.0.0.Beta8 > CLI boot, exception not thrown when error printed to error file > --------------------------------------------------------------- > > Key: WFCORE-4831 > URL: https://issues.redhat.com/browse/WFCORE-4831 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Critical > Fix For: 11.0.0.Beta8 > > > During boot CLI script processing, if an error is printed to the error file, the error is printed but the server doesn't abort. This is not correct, the server must abort. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13051) provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService

by nimo stephan (Jira)

nimo stephan created WFLY-13051: ----------------------------------- Summary: provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService Key: WFLY-13051 URL: https://issues.redhat.com/browse/WFLY-13051 Project: WildFly Issue Type: Enhancement Components: Concurrency Utilities Affects Versions: 19.0.0.Beta1 Reporter: nimo stephan Assignee: Eduardo Martins Using {code:java} @Resource private ManagedScheduledExecutorService executor; {code} provides no possiblity to setRemoveOnCancelPolicy to true. A casting within a method: {code:java} ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true); {code} throws the error: {code:java} Caused by: javax.ejb.EJBException: java.lang.ClassCastException: class org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter cannot be cast to class java.util.concurrent.ScheduledThreadPoolExecutor (org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter is in unnamed module of loader 'org.glassfish.javax.enterprise.concurrent' @a93b7af; java.util.concurrent.ScheduledThreadPoolExecutor is in module java.base of loader 'bootstrap') at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388) at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) {code} Please provide option to cast or if not possible to add the property {code:java} setRemoveOnCancelPolicy() {code} within the object ManagedScheduledExecutorService. Because without it, we cannot remove a task from the queue with "future.cancel(false)". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4919) Long running query at kie-server startup

by Jonathan Fisher (Jira)

[ https://issues.redhat.com/browse/DROOLS-4919?page=com.atlassian.jira.plug... ] Jonathan Fisher commented on DROOLS-4919: ----------------------------------------- Still hoping for an answer on this. We have to stagger our kie-server startups because a huge amount of data is being read off that table. Thank you, -Jonathan > Long running query at kie-server startup > ---------------------------------------- > > Key: DROOLS-4919 > URL: https://issues.redhat.com/browse/DROOLS-4919 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.28.0.Final > Reporter: Danny Rucker > Assignee: Maciej Swiderski > Priority: Major > > The following query is executed at start up of kie-server > ``` > select vil.processInstanceId, vil.processId, vil.id, vil.variableId, vil.value from VariableInstanceLog vil where vil.id in (select MAX(v.id) from VariableInstanceLog v group by v.variableId, v.processInstanceId) > ``` > This is causing some issues with getting kie-server to start up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4988) Test Scenario: improve DMN validation

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4988?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4988: -------------------------------- Description: Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too Use case to cover: - data type customString in a DMN defined as alias of String - test scenario created (customString will generate a single column because it is a simple type) - data type changed of customString to structure - validation error in test scenario We will need to check also validation of test scenario expression columns (= column where user map the whole object) EDIT: String to List<String> should be already covered by current validation implementation was:Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too > Test Scenario: improve DMN validation > ------------------------------------- > > Key: DROOLS-4988 > URL: https://issues.redhat.com/browse/DROOLS-4988 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too > Use case to cover: > - data type customString in a DMN defined as alias of String > - test scenario created (customString will generate a single column because it is a simple type) > - data type changed of customString to structure > - validation error in test scenario > We will need to check also validation of test scenario expression columns (= column where user map the whole object) > EDIT: > String to List<String> should be already covered by current validation implementation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4988) Test Scenario: improve DMN validation

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4988?page=com.atlassian.jira.plug... ] Daniele Zonca edited comment on DROOLS-4988 at 2/3/20 11:08 AM: ---------------------------------------------------------------- [~jomarko] Use case to cover: - data type {{customString}} in a DMN defined as alias of String - test scenario created ({{customString}} will generate a single column because it is a simple type) - data type changed of {{customString}} to structure - validation error in test scenario We will need to check also validation of test scenario expression columns (= column where user map the whole object) EDIT: String to List<String> should be already covered by current validation implementation was (Author: danielezonca): [~jomarko] Use case to cover: - data type {{customString}} in a DMN defined as alias of String - test scenario created ({{customString}} will generate a single column because it is a simple type) - data type changed of {{customString}} to structure - validation error in test scenario We will need to check also validation of test scenario expression columns (= column where user map the whole object) > Test Scenario: improve DMN validation > ------------------------------------- > > Key: DROOLS-4988 > URL: https://issues.redhat.com/browse/DROOLS-4988 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4988) Test Scenario: improve DMN validation

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4988?page=com.atlassian.jira.plug... ] Daniele Zonca commented on DROOLS-4988: --------------------------------------- [~jomarko] Use case to cover: - data type {{customString}} in a DMN defined as alias of String - test scenario created ({{customString}} will generate a single column because it is a simple type) - data type changed of {{customString}} to structure - validation error in test scenario We will need to check also validation of test scenario expression columns (= column where user map the whole object) > Test Scenario: improve DMN validation > ------------------------------------- > > Key: DROOLS-4988 > URL: https://issues.redhat.com/browse/DROOLS-4988 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4832) Two error dialog messages when DC is starting and user executes lifecycle operations on slave servers

by Yeray Borges (Jira)

Yeray Borges created WFCORE-4832: ------------------------------------ Summary: Two error dialog messages when DC is starting and user executes lifecycle operations on slave servers Key: WFCORE-4832 URL: https://issues.redhat.com/browse/WFCORE-4832 Project: WildFly Core Issue Type: Bug Reporter: Yeray Borges Assignee: Jeff Mesnil When the DC is starting, any lifecycle operation on a server that belongs to a slave shows two error dialogs, one with a description and the other without any explanation. This is more a user experience issue. Only one message dialog should be displayed under this scenario. In order to correctly test this scenario, ensure that these two issues are merged: WFCORE-4830 and WFCORE-4764 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 February 2020