June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4105) SME Review Tech Doc

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4105?page=com.atlassian.jira.plugi... ] Edoardo Vacchi resolved DROOLS-4105. ------------------------------------ Resolution: Done added comments to PR > SME Review Tech Doc > ------------------- > > Key: DROOLS-4105 > URL: https://issues.jboss.org/browse/DROOLS-4105 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Review docs in BXMSDOC-4211 sect.2-3 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4144) [DMN Designer] Imported model is broken after saving changes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4144?page=com.atlassian.jira.plugi... ] Michael Anstis edited comment on DROOLS-4144 at 6/7/19 7:10 AM: ---------------------------------------------------------------- {{org.kie.workbench.common.dmn.api.factory.AbstractDMNDiagramFactory}} assumes the default XML namespace prefix is _reserved_ for the namespace of the DMN model. This works fine in most circumstances (all circumstances of models authored with our tooling) however in the example files the default XML namespace is used to for DMN. This is overwritten by {{AbstractDMNDiagramFactory}} when the file is opened. This is wrong. Furthermore {{org.kie.dmn.backend.marshalling.v1_2.xstream.XStreamMarshaller}} attempts to read the DMN namespace prefix from the NSContext entries where the URI matches the DMN URI. If none is found it assumes it to be an empty {{String}} and adds a default namespace entry to the resulting XML for DMN. A match is never found as {{AbstractDMNDiagramFactory}} set the default XML namespace to be the DMN model namespace. Consequentially {{XStreamMarshaller}} writes two default namespaces; one for DMN and one for the DMN model namespace as set by {{AbstractDMNDiagramFactory}}. Ideally {{AbstractDMNDiagramFactory}} should not assume the default XML namespace is for its exclusive use. A workaround is to ensure the files being used set the DMN namespace prefix to {{dmn}}. e.g. <definitions xmlns:dmn="http://www.omg.org/spec/DMN/20151101/dmn.xsd" ../> This would also mean the DMN XML elements in the file would need their names prefixed with the namespace e.g. <inputData> would need to become <dmn:inputData> etc. was (Author: manstis): {{org.kie.workbench.common.dmn.api.factory.AbstractDMNDiagramFactory}} assumes the default XML namespace prefix is _reserved_ for the namespace of the DMN model. This works fine in most circumstances (all circumstances of models authored with our tooling) however in the example files the default XML namespace is used to for DMN. This is overwritten by {{AbstractDMNDiagramFactory}} when the file is opened. This is wrong. Furthermore {{org.kie.dmn.backend.marshalling.v1_2.xstream.XStreamMarshaller}} attempts to read the DMN namespace prefix from the NSContext entries where the URI matches the DMN URI. If none is found it assumes it to be an empty {{String}} and adds a default namespace entry to the resulting XML for DMN. A match is never found as {{AbstractDMNDiagramFactory}} set the default XML namespace to be the DMN model namespace. Consequentially {{XStreamMarshaller}} writes two default namespaces; one for DMN and one for the DMN model namespace as set by {{AbstractDMNDiagramFactory}}. Ideally {{AbstractDMNDiagramFactory}} should not assume the default XML namespace is for its exclusive use. A workaround is to ensure the files being used set the DMN namespace prefix to {{dmn}}. e.g. {{<definitions xmlns:dmn="http://www.omg.org/spec/DMN/20151101/dmn.xsd" ../>}} > [DMN Designer] Imported model is broken after saving changes > ------------------------------------------------------------ > > Key: DROOLS-4144 > URL: https://issues.jboss.org/browse/DROOLS-4144 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: a-2.dmn, a.dmn, error.log > > > When user imports some dmn model (see the attahced a.dmn and a-2.dmn) then he do some changes and save such imported model. He is unable to reopen such model. There is error in the server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4131) Can't use "is contained in the list" for Integer field

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4131?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4131: -------------------------------- Git Pull Request: https://github.com/kiegroup/drools-wb/pull/1165, https://github.com/kiegroup/drools/pull/2379 (was: https://github.com/kiegroup/drools-wb/pull/1165) > Can't use "is contained in the list" for Integer field > ------------------------------------------------------ > > Key: DROOLS-4131 > URL: https://issues.jboss.org/browse/DROOLS-4131 > Project: Drools > Issue Type: Bug > Components: Guided Template Editor > Affects Versions: 7.23.0.Final > Reporter: Yevgeniy Fomin > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > Attachments: ResultAfterFirstPR.webm, Screenshot from 2019-06-05 16-04-55.png, Screenshot from 2019-06-05 16-05-17.png, Screenshot from 2019-06-05 16-06-23.png, Screenshot from 2019-06-05 16-06-50.png > > > Can't use "Template key" as a list when using option "is contained in the (comma separated) list" for Integer field of Data Object in Guided Rule Templates -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4144) [DMN Designer] Imported model is broken after saving changes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4144?page=com.atlassian.jira.plugi... ] Michael Anstis edited comment on DROOLS-4144 at 6/7/19 6:58 AM: ---------------------------------------------------------------- {{org.kie.workbench.common.dmn.api.factory.AbstractDMNDiagramFactory}} assumes the default XML namespace prefix is _reserved_ for the namespace of the DMN model. This works fine in most circumstances (all circumstances of models authored with our tooling) however in the example files the default XML namespace is used to for DMN. This is overwritten by {{AbstractDMNDiagramFactory}} when the file is opened. This is wrong. Furthermore {{org.kie.dmn.backend.marshalling.v1_2.xstream.XStreamMarshaller}} attempts to read the DMN namespace prefix from the NSContext entries where the URI matches the DMN URI. If none is found it assumes it to be an empty {{String}} and adds a default namespace entry to the resulting XML for DMN. A match is never found as {{AbstractDMNDiagramFactory}} set the default XML namespace to be the DMN model namespace. Consequentially {{XStreamMarshaller}} writes two default namespaces; one for DMN and one for the DMN model namespace as set by {{AbstractDMNDiagramFactory}}. Ideally {{AbstractDMNDiagramFactory}} should not assume the default XML namespace is for its exclusive use. A workaround is to ensure the files being used set the DMN namespace prefix to {{dmn}}. e.g. {{<definitions xmlns:dmn="http://www.omg.org/spec/DMN/20151101/dmn.xsd" ../>}} was (Author: manstis): {{org.kie.workbench.common.dmn.api.factory.AbstractDMNDiagramFactory}} assumes the default XML namespace prefix is _reserved_ for the namespace of the DMN model. This works fine in most circumstances (all circumstances of models authored with our tooling) however in the example files the default XML namespace is used to qualify the DMN model. This is overwritten by {{AbstractDMNDiagramFactory}} when the file is opened. This is wrong. Furthermore {{org.kie.dmn.backend.marshalling.v1_2.xstream.XStreamMarshaller}} attempts to read the DMN namespace prefix from the NSContext entries where the URI matches the DMN URI. If none is found it assumes it to be an empty {{String}} and adds a default namespace entry to the resulting XML. A match is never found as {{AbstractDMNDiagramFactory}} set the default XML namespace to be the DMN model namespace. Consequentially {{XStreamMarshaller}} writes two default namespaces; one for DMN and one for the DMN model namespace as set by {{AbstractDMNDiagramFactory}}. Ideally {{AbstractDMNDiagramFactory}} should not assume the default XML namespace is for its exclusive use. A workaround is to ensure the files being used set the DMN namespace prefix to {{dmn}}. e.g. {{<definitions xmlns:dmn="http://www.omg.org/spec/DMN/20151101/dmn.xsd" ../>}} > [DMN Designer] Imported model is broken after saving changes > ------------------------------------------------------------ > > Key: DROOLS-4144 > URL: https://issues.jboss.org/browse/DROOLS-4144 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: a-2.dmn, a.dmn, error.log > > > When user imports some dmn model (see the attahced a.dmn and a-2.dmn) then he do some changes and save such imported model. He is unable to reopen such model. There is error in the server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4144) [DMN Designer] Imported model is broken after saving changes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4144?page=com.atlassian.jira.plugi... ] Michael Anstis edited comment on DROOLS-4144 at 6/7/19 6:57 AM: ---------------------------------------------------------------- {{org.kie.workbench.common.dmn.api.factory.AbstractDMNDiagramFactory}} assumes the default XML namespace prefix is _reserved_ for the namespace of the DMN model. This works fine in most circumstances (all circumstances of models authored with our tooling) however in the example files the default XML namespace is used to qualify the DMN model. This is overwritten by {{AbstractDMNDiagramFactory}} when the file is opened. This is wrong. Furthermore {{org.kie.dmn.backend.marshalling.v1_2.xstream.XStreamMarshaller}} attempts to read the DMN namespace prefix from the NSContext entries where the URI matches the DMN URI. If none is found it assumes it to be an empty {{String}} and adds a default namespace entry to the resulting XML. A match is never found as {{AbstractDMNDiagramFactory}} set the default XML namespace to be the DMN model namespace. Consequentially {{XStreamMarshaller}} writes two default namespaces; one for DMN and one for the DMN model namespace as set by {{AbstractDMNDiagramFactory}}. Ideally {{AbstractDMNDiagramFactory}} should not assume the default XML namespace is for its exclusive use. A workaround is to ensure the files being used set the DMN namespace prefix to {{dmn}}. e.g. {{<definitions xmlns:dmn="http://www.omg.org/spec/DMN/20151101/dmn.xsd" ../>}} was (Author: manstis): {{org.kie.workbench.common.dmn.api.factory.AbstractDMNDiagramFactory}} assumes the default XML namespace prefix is _reserved_ for the namespace of the DMN model. This works fine in most circumstances (all circumstances of models authored with our tooling) however in the example files the default XML namespace is used to qualify the DMN model. This is overwritten by {{AbstractDMNDiagramFactory}} when the file is opened. This is wrong. Furthermore {{org.kie.dmn.backend.marshalling.v1_2.xstream.XStreamMarshaller}} attempts to read the DMN namespace prefix from the NSContext entries where the URI matches the DMN URI. If none is found it assumes it to be an empty {{String}} and adds a default namespace entry to the resulting XML. A match is never found as {{AbstractDMNDiagramFactory}} set the default XML namespace to be the DMN model namespace. Consequentially {{XStreamMarshaller}} writes two default namespaces; one for DMN and one for the DMN model namespace as set by {{AbstractDMNDiagramFactory}}. Ideally {{AbstractDMNDiagramFactory}} should not assume the default XML namespace is for its exclusive use. A workaround is to ensure the files being used set the DMN namespace prefix to {{dmn}}. e.g. {{<definitions xmlns="http://www.omg.org/spec/DMN/20151101/dmn.xsd" ../>}} > [DMN Designer] Imported model is broken after saving changes > ------------------------------------------------------------ > > Key: DROOLS-4144 > URL: https://issues.jboss.org/browse/DROOLS-4144 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: a-2.dmn, a.dmn, error.log > > > When user imports some dmn model (see the attahced a.dmn and a-2.dmn) then he do some changes and save such imported model. He is unable to reopen such model. There is error in the server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4144) [DMN Designer] Imported model is broken after saving changes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4144?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-4144: -------------------------------------- Assignee: Daniel José dos Santos (was: Michael Anstis) > [DMN Designer] Imported model is broken after saving changes > ------------------------------------------------------------ > > Key: DROOLS-4144 > URL: https://issues.jboss.org/browse/DROOLS-4144 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: a-2.dmn, a.dmn, error.log > > > When user imports some dmn model (see the attahced a.dmn and a-2.dmn) then he do some changes and save such imported model. He is unable to reopen such model. There is error in the server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4144) [DMN Designer] Imported model is broken after saving changes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4144?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-4144: ---------------------------------------- {{org.kie.workbench.common.dmn.api.factory.AbstractDMNDiagramFactory}} assumes the default XML namespace prefix is _reserved_ for the namespace of the DMN model. This works fine in most circumstances (all circumstances of models authored with our tooling) however in the example files the default XML namespace is used to qualify the DMN model. This is overwritten by {{AbstractDMNDiagramFactory}} when the file is opened. This is wrong. Furthermore {{org.kie.dmn.backend.marshalling.v1_2.xstream.XStreamMarshaller}} attempts to read the DMN namespace prefix from the NSContext entries where the URI matches the DMN URI. If none is found it assumes it to be an empty {{String}} and adds a default namespace entry to the resulting XML. A match is never found as {{AbstractDMNDiagramFactory}} set the default XML namespace to be the DMN model namespace. Consequentially {{XStreamMarshaller}} writes two default namespaces; one for DMN and one for the DMN model namespace as set by {{AbstractDMNDiagramFactory}}. Ideally {{AbstractDMNDiagramFactory}} should not assume the default XML namespace is for its exclusive use. A workaround is to ensure the files being used set the DMN namespace prefix to {{dmn}}. e.g. {{<definitions xmlns="http://www.omg.org/spec/DMN/20151101/dmn.xsd" ../>}} > [DMN Designer] Imported model is broken after saving changes > ------------------------------------------------------------ > > Key: DROOLS-4144 > URL: https://issues.jboss.org/browse/DROOLS-4144 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: a-2.dmn, a.dmn, error.log > > > When user imports some dmn model (see the attahced a.dmn and a-2.dmn) then he do some changes and save such imported model. He is unable to reopen such model. There is error in the server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4144) [DMN Designer] Imported model is broken after saving changes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4144?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-4144: ---------------------------------------- Saving the file adds two default namespaces: {code} <definitions xmlns="http://www.omg.org/spec/DMN/20180521/MODEL/" xmlns="https://www.drools.org/kie-dmn/Flight-rebooking" .../> {code} > [DMN Designer] Imported model is broken after saving changes > ------------------------------------------------------------ > > Key: DROOLS-4144 > URL: https://issues.jboss.org/browse/DROOLS-4144 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: a-2.dmn, a.dmn, error.log > > > When user imports some dmn model (see the attahced a.dmn and a-2.dmn) then he do some changes and save such imported model. He is unable to reopen such model. There is error in the server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4144) [DMN Designer] Imported model is broken after saving changes

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4144: ----------------------------------- Summary: [DMN Designer] Imported model is broken after saving changes Key: DROOLS-4144 URL: https://issues.jboss.org/browse/DROOLS-4144 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.24.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: a-2.dmn, a.dmn, error.log When user imports some dmn model (see the attahced a.dmn and a-2.dmn) then he do some changes and save such imported model. He is unable to reopen such model. There is error in the server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4143) Strange error when generateModel=NO

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4143?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4143: -------------------------------- Sprint: 2019 Week 23-25 > Strange error when generateModel=NO > ----------------------------------- > > Key: DROOLS-4143 > URL: https://issues.jboss.org/browse/DROOLS-4143 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Daniele Zonca > Assignee: Mario Fusco > Priority: Major > > Reproducer > https://github.com/danielezonca/tempproject/ > Change in the pom.xml generateModel to NO to have the error -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019