June 2020 - jboss-jira - Jboss List Archives

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

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ] Eduardo Martins commented on WFLY-13051: ---------------------------------------- [~nimo22] sorry, it's not possible, and after internal team discussion we agreed allowing apps to reach internal executors would lock us on implementation details and could introduce other issues (e.g. security). If you really need to remove tasks when canceled (instead of when these expire) the work around possible would be for your app or custom extension to manage a ScheduledThreadPoolExecutor and use the ContextService to make tasks contextual (if needed). Not sure such workaround would have a significant performance advantage tho... > 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 > Priority: Major > > 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)

4 years, 7 months

1
0
0 / 0

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

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ] Eduardo Martins closed WFLY-13051. ---------------------------------- Resolution: Won't Do > 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 > Priority: Major > > 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)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3685: ------------------------------------ Attachment: columns2.png > [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3685 > URL: https://issues.redhat.com/browse/DROOLS-3685 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Valentino Pellegrino > Priority: Major > Labels: drools-tools > Attachments: 2020-05-21-14.57.31.gif, columns.png, columns.png, columns2.png, data-types.png, license.dmn > > > When creating a decision table, output clauses columns should be created based on the type of the output node. > This is what we are already doing for the input columns, that are created based on the type of the input node. > h3. Acceptance criteria > - Output ref is a simple built in type > - Output ref is simple but custom type > - Output ref is a structure with simple type fields > - Output ref is structure with custom type type fields > The flow for the input columns is described in the GIF below: > !2020-05-21-14.57.31.gif|height=450,width=950! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5396) Undo and Redo keyboard shortcuts do not work in grid editor

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5396: ----------------------------------- Summary: Undo and Redo keyboard shortcuts do not work in grid editor Key: DROOLS-5396 URL: https://issues.redhat.com/browse/DROOLS-5396 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.39.0.Final Reporter: Jozef Marko Assignee: Guilherme Gomes We have these shortcuts in DMN designer - Undo Ctrl+Z - Redo Ctrl+Shift+Z They work fine on graph editor. However they do not work in grid editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ] Guilherme Gomes commented on DROOLS-3685: ----------------------------------------- [~jomarko], they must be different. Input clauses support FEEL expressions, and on output columns we're able to achieve just two levels of depth with data type fields. Thus [~vpellegr] is generating columns accordingly: !columns.png|width=600! > [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3685 > URL: https://issues.redhat.com/browse/DROOLS-3685 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Valentino Pellegrino > Priority: Major > Labels: drools-tools > Attachments: 2020-05-21-14.57.31.gif, columns.png, columns.png, data-types.png, license.dmn > > > When creating a decision table, output clauses columns should be created based on the type of the output node. > This is what we are already doing for the input columns, that are created based on the type of the input node. > h3. Acceptance criteria > - Output ref is a simple built in type > - Output ref is simple but custom type > - Output ref is a structure with simple type fields > - Output ref is structure with custom type type fields > The flow for the input columns is described in the GIF below: > !2020-05-21-14.57.31.gif|height=450,width=950! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5396) Undo and Redo keyboard shortcuts do not work in grid editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5396?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5396: -------------------------------- Priority: Minor (was: Major) > Undo and Redo keyboard shortcuts do not work in grid editor > ----------------------------------------------------------- > > Key: DROOLS-5396 > URL: https://issues.redhat.com/browse/DROOLS-5396 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.39.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > > We have these shortcuts in DMN designer > - Undo Ctrl+Z > - Redo Ctrl+Shift+Z > They work fine on graph editor. However they do not work in grid editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3685: ------------------------------------ Attachment: columns.png > [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3685 > URL: https://issues.redhat.com/browse/DROOLS-3685 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Valentino Pellegrino > Priority: Major > Labels: drools-tools > Attachments: 2020-05-21-14.57.31.gif, columns.png, columns.png, data-types.png, license.dmn > > > When creating a decision table, output clauses columns should be created based on the type of the output node. > This is what we are already doing for the input columns, that are created based on the type of the input node. > h3. Acceptance criteria > - Output ref is a simple built in type > - Output ref is simple but custom type > - Output ref is a structure with simple type fields > - Output ref is structure with custom type type fields > The flow for the input columns is described in the GIF below: > !2020-05-21-14.57.31.gif|height=450,width=950! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13548) Implementation of XAResourceWrapper to allow Narayana resolve in-doubt transaction assume complete situation

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13548?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka moved JBEAP-19606 to WFLY-13548: ------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13548 (was: JBEAP-19606) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: Generic JMS RA) Affects Version/s: 13.0.0.Final (was: 7.1.0.GA) > Implementation of XAResourceWrapper to allow Narayana resolve in-doubt transaction assume complete situation > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-13548 > URL: https://issues.redhat.com/browse/WFLY-13548 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Jeff Mesnil > Priority: Major > > With fix of the https://issues.jboss.org/browse/JBTM-860 there was added method {{getJndiName}} for {{XAResourceWrapper}}: https://github.com/jbosstm/jboss-transaction-spi/blob/master/src/main/jav... > which Narayana uses to resolve situation when there is in-doubt record at the side of resource manager (message broker) but Narayana does not have corresponding record in its log store. This could mean the transaction was already committed. But Narayana needs to pair the in-doubt transaction with existing RM to assume so. > This capability would be fine to be provided by generic jms ra too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-3685: ------------------------------------- [~karreiro] [~vpellegr] I am not sure if we agreed on correct behavior in the comment above. In the attached model [^license.dmn] please compare input columns and output columns of the decision table. Both were autogenerated. > [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3685 > URL: https://issues.redhat.com/browse/DROOLS-3685 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Valentino Pellegrino > Priority: Major > Labels: drools-tools > Attachments: 2020-05-21-14.57.31.gif, columns.png, data-types.png, license.dmn > > > When creating a decision table, output clauses columns should be created based on the type of the output node. > This is what we are already doing for the input columns, that are created based on the type of the input node. > h3. Acceptance criteria > - Output ref is a simple built in type > - Output ref is simple but custom type > - Output ref is a structure with simple type fields > - Output ref is structure with custom type type fields > The flow for the input columns is described in the GIF below: > !2020-05-21-14.57.31.gif|height=450,width=950! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-3685: -------------------------------- Attachment: (was: new-file.dmn) > [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3685 > URL: https://issues.redhat.com/browse/DROOLS-3685 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Valentino Pellegrino > Priority: Major > Labels: drools-tools > Attachments: 2020-05-21-14.57.31.gif, columns.png, data-types.png, license.dmn > > > When creating a decision table, output clauses columns should be created based on the type of the output node. > This is what we are already doing for the input columns, that are created based on the type of the input node. > h3. Acceptance criteria > - Output ref is a simple built in type > - Output ref is simple but custom type > - Output ref is a structure with simple type fields > - Output ref is structure with custom type type fields > The flow for the input columns is described in the GIF below: > !2020-05-21-14.57.31.gif|height=450,width=950! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020