June 2020 - jboss-jira - Jboss List Archives

[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)

6 years, 1 month

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)

6 years, 1 month

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)

6 years, 1 month

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: license.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)

6 years, 1 month

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)

6 years, 1 month

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: 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13515) Application does not fail when @Singleton @PostConstruct throws exception

by Panagiotis Sotiropoulos (Jira)

[ https://issues.redhat.com/browse/WFLY-13515?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos commented on WFLY-13515: ------------------------------------------------ Adding a manual server mvtc : https://github.com/jboss-set/eap-additional-testsuite/pull/144 > Application does not fail when @Singleton @PostConstruct throws exception > ------------------------------------------------------------------------- > > Key: WFLY-13515 > URL: https://issues.redhat.com/browse/WFLY-13515 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 19.0.0.Final, 20.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Panagiotis Sotiropoulos > Priority: Major > Labels: Regression > Attachments: helloWorld.ear > > > In EAP 6.4 , sub deployments were accessible before all Singleton's PostConstruct were finished, this was fixed via [1]. After this fix if an exception was thrown from PostConstruct, then the whole deployment was in a failed state as well. EAP 7.0 works the same as EAP 6.4 after the fix. > In EAP 7.3/7.2/7.1 when the Singleton throws an exception, the sub deployments are accessible. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1310908 > EJB 3.1 spec, section 4.8.1: > {quote} > If the Startup annotation appears on the Singleton bean class or if the Singleton has been designated via the deployment descriptor as requiring eager initialization, the container must initialize the Singleton bean instance during the application startup sequence. The container must initialize all such startup-time Singletons before any external client requests (that is, client requests originating outside of the application) are delivered to any enterprise bean components in the application. > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4916) Unclear attribute name completion for LIST type

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4916?page=com.atlassian.jira.plug... ] Jean Francois Denise updated WFCORE-4916: ----------------------------------------- Issue Type: Enhancement (was: Bug) > Unclear attribute name completion for LIST type > ----------------------------------------------- > > Key: WFCORE-4916 > URL: https://issues.redhat.com/browse/WFCORE-4916 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 12.0.0.Beta1 > Reporter: Chao Wang > Assignee: Jean Francois Denise > Priority: Minor > > Following discussion in WFCORE-4908. There is a completion of "[" for LIST type attribute name after hitting tab, for example: > {code} > [domain@localhost:9990 /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options > {code} > added here https://github.com/wildfly/wildfly-core/blob/12.0.0.Beta1/cli/src/main/ja... > It seems to me that misleads to the wrong syntax as described in WFCORE-4908. > {code} > [domain@localhost:9990 /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options[... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5395) Clear selection button doesn't work on Testing Tools when use click property first time.

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-5395: ------------------------------------ Summary: Clear selection button doesn't work on Testing Tools when use click property first time. Key: DROOLS-5395 URL: https://issues.redhat.com/browse/DROOLS-5395 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Anna Dupliak Assignee: Yeser Amer Attachments: ClearTestingTools.webm If user click to clear expression based property from Scesim Table it does not reacts anyhow in Testing Tools see [^ClearTestingTools.webm] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4916) Unclear attribute name completion for LIST type

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4916?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-4916: ---------------------------------------------- [~brian.stansberry], I agree, the completer should add the ','. This enhancement would be in line with the completer general behavior. It does it in some cases (eg: boolean with =false being set). Also, the character ')' is added when no more attributes can be set. > Unclear attribute name completion for LIST type > ----------------------------------------------- > > Key: WFCORE-4916 > URL: https://issues.redhat.com/browse/WFCORE-4916 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 12.0.0.Beta1 > Reporter: Chao Wang > Assignee: Jean Francois Denise > Priority: Minor > > Following discussion in WFCORE-4908. There is a completion of "[" for LIST type attribute name after hitting tab, for example: > {code} > [domain@localhost:9990 /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options > {code} > added here https://github.com/wildfly/wildfly-core/blob/12.0.0.Beta1/cli/src/main/ja... > It seems to me that misleads to the wrong syntax as described in WFCORE-4908. > {code} > [domain@localhost:9990 /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options[... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 June 2020