April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1601) Support constraints on List inputs in DT cells

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1601?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1601: ------------------------------------------- Fix Version/s: 7.8.0.Final (was: 7.7.0.Final) > Support constraints on List inputs in DT cells > ---------------------------------------------- > > Key: DROOLS-1601 > URL: https://issues.jboss.org/browse/DROOLS-1601 > Project: Drools > Issue Type: Sub-task > Components: dmn engine > Affects Versions: 7.1.0.Beta2 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.8.0.Final > > > Make sure the unary tests in the decision tables work fine with list inputs. This ticket might require no changes on our side, but we should at least add a couple tests to avoid regressions in the future. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1600) Support character ? for interpolation in values in a DT cell

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1600?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1600: ------------------------------------------- Fix Version/s: 7.8.0.Final (was: 7.7.0.Final) > Support character ? for interpolation in values in a DT cell > ------------------------------------------------------------ > > Key: DROOLS-1600 > URL: https://issues.jboss.org/browse/DROOLS-1600 > Project: Drools > Issue Type: Sub-task > Components: dmn engine > Affects Versions: 7.1.0.Beta2 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.8.0.Final > > Attachments: Screenshot 2017-06-02 19.50.40.png > > > Signavio uses the character ? to interpolate the expression value into decision table cells. E.g.: > =(1 - Discount) * ? > In the above example, '?' is replaced my the result of the decision table input expression. > See attached screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-115) Update Ansible to 2.5 on Jenkins Slaves

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-115?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-115: -------------------------------- Team: Infrastructure (was: Infrastructure) Sprint: Kiali QE Sprint 3 > Update Ansible to 2.5 on Jenkins Slaves > ---------------------------------------- > > Key: SWSQE-115 > URL: https://issues.jboss.org/browse/SWSQE-115 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > > Hi [~fbrychta], > I needed to update ansible from 2.4 to 2.5 in order to make Test Mesh playbook to work > {panel:title=ansible 2.4.2.0} > config file = /etc/ansible/ansible.cfg > configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] > ansible python module location = /usr/lib/python2.7/site-packages/ansible > executable location = /usr/bin/ansible > python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)] > By executing the test_mesh ansible playbook, I get a syntax error: > {code:shell} > ansible-playbook test_mesh.yml --syntax-check > ERROR! The field 'loop' is supposed to be a string type, however the incoming data structure is a <class 'ansible.parsing.yaml.objects.AnsibleSequence'> > {code} > {panel} > {panel:title=ansible 2.5.0} > config file = /etc/ansible/ansible.cfg > configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] > ansible python module location = /usr/lib/python2.7/site-packages/ansible > executable location = /bin/ansible > python version = 2.7.14 (default, Mar 14 2018, 13:36:31) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)] > On Ansible 2.5.0, I don't get the error > {code} > ansible-playbook test_mesh.yml --syntax-check > playbook: test_mesh.yml (executes it fine) > {code} > {panel} > I know that Ansible 2.5.0 was released some days ago, so if we are using on RHEL, maybe it would need to update it from sources, even Brew or Pulp. I was able to track ansible repository (http://pulp.dist.prod.ext.phx2.redhat.com/content/dist/rhel/server/7/7Ser...) but I had no success installing it on slave2. > On Fedora, it is widespread on the "main repositories" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-115) Update Ansible to 2.5 on Jenkins Slaves

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-115?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-115. --------------------------------- Resolution: Done Updated jenkins slaves + ansible --version ansible 2.5.0 config file = /etc/ansible/ansible.cfg configured module search path = [u'/home/jenkins/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, Aug 4 2017, 00:39:18) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > Update Ansible to 2.5 on Jenkins Slaves > ---------------------------------------- > > Key: SWSQE-115 > URL: https://issues.jboss.org/browse/SWSQE-115 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > > Hi [~fbrychta], > I needed to update ansible from 2.4 to 2.5 in order to make Test Mesh playbook to work > {panel:title=ansible 2.4.2.0} > config file = /etc/ansible/ansible.cfg > configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] > ansible python module location = /usr/lib/python2.7/site-packages/ansible > executable location = /usr/bin/ansible > python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)] > By executing the test_mesh ansible playbook, I get a syntax error: > {code:shell} > ansible-playbook test_mesh.yml --syntax-check > ERROR! The field 'loop' is supposed to be a string type, however the incoming data structure is a <class 'ansible.parsing.yaml.objects.AnsibleSequence'> > {code} > {panel} > {panel:title=ansible 2.5.0} > config file = /etc/ansible/ansible.cfg > configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] > ansible python module location = /usr/lib/python2.7/site-packages/ansible > executable location = /bin/ansible > python version = 2.7.14 (default, Mar 14 2018, 13:36:31) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)] > On Ansible 2.5.0, I don't get the error > {code} > ansible-playbook test_mesh.yml --syntax-check > playbook: test_mesh.yml (executes it fine) > {code} > {panel} > I know that Ansible 2.5.0 was released some days ago, so if we are using on RHEL, maybe it would need to update it from sources, even Brew or Pulp. I was able to track ansible repository (http://pulp.dist.prod.ext.phx2.redhat.com/content/dist/rhel/server/7/7Ser...) but I had no success installing it on slave2. > On Fedora, it is widespread on the "main repositories" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2448) Validator for schema to provide an embed version of the DMN XSD

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2448: -------------------------------------- Summary: Validator for schema to provide an embed version of the DMN XSD Key: DROOLS-2448 URL: https://issues.jboss.org/browse/DROOLS-2448 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Priority: Minor Currently the DMN Validator for schema validation requires to specify in the XML of the DMN model the schema location, like for example: {code:java} xsi:schemaLocation="http://www.omg.org/spec/DMN/20151101/dmn.xsd https://www.omg.org/spec/DMN/20151101/dmn.xsd " {code} as an attribute of the root {{definitions}} xml element. This could be improved for the DMN Validator to check the schema against an embedded version of the XSD, instead of relying on the supplied schemaLocation in the xml. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2447) Validator for schema to provide an embed version of the DMN XSD

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2447: -------------------------------------- Summary: Validator for schema to provide an embed version of the DMN XSD Key: DROOLS-2447 URL: https://issues.jboss.org/browse/DROOLS-2447 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Edson Tirelli Priority: Minor Currently the DMN Validator for schema validation requires to specify in the XML of the DMN model the schema location, like for example: {code:java} xsi:schemaLocation="http://www.omg.org/spec/DMN/20151101/dmn.xsd https://www.omg.org/spec/DMN/20151101/dmn.xsd " {code} as an attribute of the root {{definitions}} xml element. It would be a -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2419) Validator fails schema validation for definition xml element with prefix

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2419?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2419: ----------------------------------- Sprint: 2018 Week 13-14 > Validator fails schema validation for definition xml element with prefix > ------------------------------------------------------------------------ > > Key: DROOLS-2419 > URL: https://issues.jboss.org/browse/DROOLS-2419 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Attachments: UsingSemanticNS.dmn > > > Given the attached model and the following test > {code:java} > @Test > public void testTEMP() { > List<DMNMessage> validate = validator.validate(getReader("UsingSemanticNS.dmn"), VALIDATE_SCHEMA, VALIDATE_MODEL, VALIDATE_COMPILATION); > assertThat(ValidatorUtil.formatMessages(validate), validate.size(), is(0)); > } > {code} > fails with: > {code:java} > java.lang.AssertionError: DMNMessage{ severity=ERROR, type=FAILED_XML_VALIDATION, message='Failed XML validation of DMN file: cvc-elt.1: Cannot find the declaration of element 'semantic:definitions'.', sourceId='null', exception='SAXParseException : cvc-elt.1: Cannot find the declaration of element 'semantic:definitions'.', feelEvent=''} > Expected: is <0> > but: was <1> > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.junit.Assert.assertThat(Assert.java:956) > at org.kie.dmn.validation.ValidatorTest.testTEMP(ValidatorTest.java:92) > ... > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2419) Validator fails schema validation for definition xml element with prefix

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2419?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-2419: -------------------------------------- Assignee: Matteo Mortari (was: Fedor Gavrilov) > Validator fails schema validation for definition xml element with prefix > ------------------------------------------------------------------------ > > Key: DROOLS-2419 > URL: https://issues.jboss.org/browse/DROOLS-2419 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Attachments: UsingSemanticNS.dmn > > > Given the attached model and the following test > {code:java} > @Test > public void testTEMP() { > List<DMNMessage> validate = validator.validate(getReader("UsingSemanticNS.dmn"), VALIDATE_SCHEMA, VALIDATE_MODEL, VALIDATE_COMPILATION); > assertThat(ValidatorUtil.formatMessages(validate), validate.size(), is(0)); > } > {code} > fails with: > {code:java} > java.lang.AssertionError: DMNMessage{ severity=ERROR, type=FAILED_XML_VALIDATION, message='Failed XML validation of DMN file: cvc-elt.1: Cannot find the declaration of element 'semantic:definitions'.', sourceId='null', exception='SAXParseException : cvc-elt.1: Cannot find the declaration of element 'semantic:definitions'.', feelEvent=''} > Expected: is <0> > but: was <1> > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.junit.Assert.assertThat(Assert.java:956) > at org.kie.dmn.validation.ValidatorTest.testTEMP(ValidatorTest.java:92) > ... > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2425) [DMN Designer] Undo of relation column deletion is not proper

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2425?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2425: ------------------------------------- Still can reproduce, if I delete and undo deletion of decision table column that some column previously completely visible are not more visible. > [DMN Designer] Undo of relation column deletion is not proper > ------------------------------------------------------------- > > Key: DROOLS-2425 > URL: https://issues.jboss.org/browse/DROOLS-2425 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2018-03-27 12-12-05.png, Screenshot from 2018-03-27 12-14-47.png, Screenshot from 2018-03-27 12-14-55.png > > > This issue was spotted during DROOLS-2392 review. > In special cases undo of delete relation column is not proper. > h2. Acceptance test > # Steps to reproduce fixed (/) > # Deletion is undone properly > ## Deletion of con. entry (/) > ## Deletion of Dec. table row (/) > ## Deletion of Dec. table column (x) > ## Deletion of Relation column > ## Deletion of Relation row > ## Deletion of Function parameter > # Clear of expression type is undone properly -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10170) A Timer will hang forever if the database connection is not available

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-10170: --------------------------------------- Summary: A Timer will hang forever if the database connection is not available Key: WFLY-10170 URL: https://issues.jboss.org/browse/WFLY-10170 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 12.0.0.Final Reporter: Wolf-Dieter Fink Assignee: Jörg Bäsner Fix For: 13.0.0.Beta1 Having a Timer annotated like: {code} @Schedule(second = "*/15", minute = "*", hour = "*", persistent = true) public void timeoutMethod() { {code} and a server configuration like: {code:xml} <timer-service thread-pool-name="default" default-data-store="clustered-store"> <data-stores> <database-data-store name="clustered-store" datasource-jndi-name="java:jboss/datasources/ExampleDS"/> </data-stores> </timer-service> {code} will lead to a hanging Timer in case the Database connection is not available and only a restart of the server will recover the Timer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 April 2018