December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2161) Recursive function definitions in context entries are raising compile time errors

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-2161: ------------------------------------- Summary: Recursive function definitions in context entries are raising compile time errors Key: DROOLS-2161 URL: https://issues.jboss.org/browse/DROOLS-2161 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.4.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Attachments: ContextRecursion.dmn Recursive function definitions in contexts are raising compile time errors but are executing correctly. See attached model for example. Functions "f" and "h" raise compile time errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1597) Implement profile for integration with Signavio's DMN modeler

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1597?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1597: ---------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48) > Implement profile for integration with Signavio's DMN modeler > ------------------------------------------------------------- > > Key: DROOLS-1597 > URL: https://issues.jboss.org/browse/DROOLS-1597 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.1.0.Beta2 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.5.0.Final > > > Signavio implements a number of extensions to the DMN standard. As they are a Red Hat partner, we will need to implement a profile in the runtime engine that enables and supports those extensions. > A short list of extensions is as follows. Details will be added to individual tickets: > * Support additional FEEL functions and alternate names for existing functions > * Support the Multi Instance Decision node > * Support character '?' for interpolation of values in a DT cell > * Support constraints on List inputs in DT cells > * Support model composition through BKMs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2160) Enhance UI in Test Scenarios Editor

by Ivo Bek (JIRA)

Ivo Bek created DROOLS-2160: ------------------------------- Summary: Enhance UI in Test Scenarios Editor Key: DROOLS-2160 URL: https://issues.jboss.org/browse/DROOLS-2160 Project: Drools Issue Type: Enhancement Components: Test Scenarios Editor Reporter: Ivo Bek Assignee: Toni Rikkola Attachments: Screenshot from 2017-12-01 16-38-52.png Test Scenarios editor needs to be polished: * Delete Buttons are too small - it would be good to enlarge them. * Some other elements doesn't have enough space around them. * Please do any other small visual changes which makes sense. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2160) Enhance UI in Test Scenarios Editor

by Ivo Bek (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2160?page=com.atlassian.jira.plugi... ] Ivo Bek commented on DROOLS-2160: --------------------------------- + [~jomarko] > Enhance UI in Test Scenarios Editor > ----------------------------------- > > Key: DROOLS-2160 > URL: https://issues.jboss.org/browse/DROOLS-2160 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Ivo Bek > Assignee: Toni Rikkola > Attachments: Screenshot from 2017-12-01 16-38-52.png > > > Test Scenarios editor needs to be polished: > * Delete Buttons are too small - it would be good to enlarge them. > * Some other elements doesn't have enough space around them. > * Please do any other small visual changes which makes sense. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9590) Auto-[create|delete]-jms-queues cannot be disabled

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9590?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-13898 to WFLY-9590: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9590 (was: JBEAP-13898) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) (was: JMS) Affects Version/s: (was: 7.2.0.GA) > Auto-[create|delete]-jms-queues cannot be disabled > -------------------------------------------------- > > Key: WFLY-9590 > URL: https://issues.jboss.org/browse/WFLY-9590 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > > For more information about origin of this issue see JBEAP-13856. > Auto-create-jms-queues and auto-delete-jms-queues enable or disable automatic creation or deletion of JMS queues when they are requested or when they are not used anymore. > In EAP 7.1 the features are disabled by default and they are Technical previews. > In EAP 7.2 the features cannot be disabled via mentioned management attributes and thus they are always enabled. The “cannot be” in previous sentence means that the configuration has no effect. > *Customer impact:* Behavior of messaging broker was changed in case of automatic creation and deletion JMS destinations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9590) auto-[create|delete]-jms-queues are not supported in Artemis 2.4

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9590?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9590: ------------------------------ Summary: auto-[create|delete]-jms-queues are not supported in Artemis 2.4 (was: Auto-[create|delete]-jms-queues cannot be disabled) > auto-[create|delete]-jms-queues are not supported in Artemis 2.4 > ---------------------------------------------------------------- > > Key: WFLY-9590 > URL: https://issues.jboss.org/browse/WFLY-9590 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > > For more information about origin of this issue see JBEAP-13856. > Auto-create-jms-queues and auto-delete-jms-queues enable or disable automatic creation or deletion of JMS queues when they are requested or when they are not used anymore. > In EAP 7.1 the features are disabled by default and they are Technical previews. > In EAP 7.2 the features cannot be disabled via mentioned management attributes and thus they are always enabled. The “cannot be” in previous sentence means that the configuration has no effect. > *Customer impact:* Behavior of messaging broker was changed in case of automatic creation and deletion JMS destinations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2673) HTTP redirect if both http and https socket-binding is configured for http-interface

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2673?page=com.atlassian.jira.plugi... ] Bartosz Spyrko-Śmietanko reassigned WFCORE-2673: ------------------------------------------------ Assignee: (was: Bartosz Spyrko-Śmietanko) > HTTP redirect if both http and https socket-binding is configured for http-interface > ------------------------------------------------------------------------------------ > > Key: WFCORE-2673 > URL: https://issues.jboss.org/browse/WFCORE-2673 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Ondrej Lukas > > In case when both http and https socket-binding is configured for management http-interface and http port is accessed then server tries to redirect automatically to https port. Access http is not possible. > It causes that it is impossible to connect to http-interface with clients which do not supports https (even if http port is provided by application server), i.e. following ModelControllerClient is not able to connect to http-interface when both http and https socket-binding is configured: > {code} > ModelControllerClient client = ModelControllerClient.Factory > .create(new ModelControllerClientConfiguration.Builder() > .setProtocol("remote+http") > .setPort(9990) > .setHostName("localhost") > .setConnectionTimeout(10000).build()) > {code} > See: > {code} > curl -v -H 'Upgrade: jboss-remoting' http://localhost:9990 > * Rebuilt URL to: http://localhost:9990/ > * Hostname was NOT found in DNS cache > * Trying 127.0.0.1... > * Connected to localhost (127.0.0.1) port 9990 (#0) > > GET / HTTP/1.1 > > User-Agent: curl/7.38.0 > > Host: localhost:9990 > > Accept: */* > > Upgrade: jboss-remoting > > > < HTTP/1.1 302 Found > < Connection: keep-alive > < Location: https://localhost:9993/ > < Content-Length: 0 > < Date: Thu, 13 Apr 2017 11:59:56 GMT > < > * Connection #0 to host localhost left intact > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-283: -------------------------------- Few notes: * property *sun.security.jgss.native* needs to be set using JAVA_OPTS="-D ..." before standalone.sh (setting in standalone.xml is applied to late and is ignored by JVM) * to debug SunNativeProvider add property: *sun.security.nativegss.debug=true* > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2157) DMN Editor: Contexts: Add special behaviour of last row

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2157?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2157: ----------------------------------- Tester: Jozef Marko > DMN Editor: Contexts: Add special behaviour of last row > ------------------------------------------------------- > > Key: DROOLS-2157 > URL: https://issues.jboss.org/browse/DROOLS-2157 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > The last row of a {{Context}} should span all columns and populate the last {{ContextEntry}} in the {{Context}}. It should not have a variable. This is the XML for a _regular_ row and the _final_ row: > {code} > <semantic:context id="_f4f86e5f-e3e3-4b99-9260-8086764e598f"> > <semantic:contextEntry> > <semantic:variable id="_779ca919-15d8-48d0-a9f0-e0203e60fac6" name="in1"/> > <semantic:literalExpression id="_4b8b8cc1-a56c-4673-8334-96e178cd04a4"> > <semantic:text>"literal exp" </semantic:text> > </semantic:literalExpression> > </semantic:contextEntry> > <semantic:contextEntry> > <semantic:literalExpression id="_297181da-d0d5-4137-960b-34836d5570e5"> > <semantic:text>"result" </semantic:text> > </semantic:literalExpression> > </semantic:contextEntry> > </semantic:context> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2157) DMN Editor: Contexts: Add special behaviour of last row

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2157?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2157: ---------------------------------------- Changes: https://github.com/manstis/appformer/commit/b47182f6717b7c84089a7b705436e... https://github.com/manstis/kie-wb-common/commit/5618dad130f88fc435da41585... Unit tests to follow. > DMN Editor: Contexts: Add special behaviour of last row > ------------------------------------------------------- > > Key: DROOLS-2157 > URL: https://issues.jboss.org/browse/DROOLS-2157 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > The last row of a {{Context}} should span all columns and populate the last {{ContextEntry}} in the {{Context}}. It should not have a variable. This is the XML for a _regular_ row and the _final_ row: > {code} > <semantic:context id="_f4f86e5f-e3e3-4b99-9260-8086764e598f"> > <semantic:contextEntry> > <semantic:variable id="_779ca919-15d8-48d0-a9f0-e0203e60fac6" name="in1"/> > <semantic:literalExpression id="_4b8b8cc1-a56c-4673-8334-96e178cd04a4"> > <semantic:text>"literal exp" </semantic:text> > </semantic:literalExpression> > </semantic:contextEntry> > <semantic:contextEntry> > <semantic:literalExpression id="_297181da-d0d5-4137-960b-34836d5570e5"> > <semantic:text>"result" </semantic:text> > </semantic:literalExpression> > </semantic:contextEntry> > </semantic:context> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 December 2017