October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1667) FEEL expression fails: 1 + if true then 1 else 2

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1667?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1667: ----------------------------------- Sprint: 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41 (was: 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39) > FEEL expression fails: 1 + if true then 1 else 2 > ------------------------------------------------ > > Key: DROOLS-1667 > URL: https://issues.jboss.org/browse/DROOLS-1667 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Edson Tirelli > Assignee: Fedor Gavrilov > Fix For: 7.4.0.Final > > > The following FEEL expression fails to parse: > 1 + if true then 1 else 2 > Similar expressions might present the same problem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1553) Write documentation for the DMN and FEEL components

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1553?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1553: ----------------------------------- Sprint: 2017 Week 22-23, 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 (was: 2017 Week 22-23, 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) > Write documentation for the DMN and FEEL components > --------------------------------------------------- > > Key: DROOLS-1553 > URL: https://issues.jboss.org/browse/DROOLS-1553 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.0.0.CR3 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.4.0.Final > > > Write the documentation for both FEEL and DMN engines. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

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

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1597?page=com.atlassian.jira.plugi... ] Kris Verlaenen 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 (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) > 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.4.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.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3987) Regression regarding WS Client when using header authentication

by Vlastimil Eliáš (JIRA)

[ https://issues.jboss.org/browse/WFLY-3987?page=com.atlassian.jira.plugin.... ] Vlastimil Eliáš commented on WFLY-3987: --------------------------------------- [~push174] I removed 'Jboss Soap.txt' attachment due to the potential exposure of sensitive informations (Authentication http header). Feel free to attach it again without this info. > Regression regarding WS Client when using header authentication > --------------------------------------------------------------- > > Key: WFLY-3987 > URL: https://issues.jboss.org/browse/WFLY-3987 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.1.0.Final, 9.0.0.Alpha1 > Environment: Linux (Ubuntu 14.04), OpenJDK 1.7.0_65, Wildfly 8.0/8.1/9.0A > Reporter: Marcus Carlson > Assignee: Alessio Soldano > Attachments: HPD_IncidentInterface_Create_WS.wsdl, Tomcat.txt > > > I'm trying to integrate a Web Service client based on BMC Remedy product where Web service authentication is handled in Soap Header and not basic authentication. See AuthenticationInfo element on https://github.com/macmorning/itsm_mobileview/blob/master/SoapUI%20Projec... for an example of how the WSDL file looks like. > I've enabled Xadditionalheaders so I get the AuthenticationInfo as the last argument, like this: > {noformat} > port.helpDeskQueryListService(qualification, startRecord, maxLimit, authInfo); > {noformat} > Problem is that this was working fine in WildFly 8.0 generating the following SOAP Request: > {noformat} > ID: 1 > Address: https://SERVER/arsys/services/ARService?server=SERVER&webService=HPD_Inci... > Encoding: UTF-8 > Http-Method: POST > Content-Type: text/xml > Headers: {Accept=[*/*], SOAPAction=["urn:HPD_IncidentInterface_WS/HelpDesk_QueryList_Service"]} > Payload: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><AuthenticationInfo xmlns="urn:HPD_IncidentInterface_WS"><userName>SECRETUSER</userName><password>SECRETPASSWORD</password></AuthenticationInfo></soap:Header><soap:Body><HelpDesk_QueryList_Service xmlns="urn:HPD_IncidentInterface_WS"><Qualification>'Status' = "Closed"</Qualification><startRecord>0</startRecord><maxLimit>1000</maxLimit></HelpDesk_QueryList_Service></soap:Body></soap:Envelope> > {noformat} > With 8.1 it's generating a completly different payload with the Header element in Body and body completly missing (!): > {noformat} > ID: 2 > Address: https://SERVER/arsys/services/ARService?server=SERVER&webService=HPD_Inci... > Encoding: UTF-8 > Http-Method: POST > Content-Type: text/xml > Headers: {Accept=[*/*], SOAPAction=["urn:HPD_IncidentInterface_WS/HelpDesk_QueryList_Service"]} > Payload: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><HelpDesk_QueryList_Service xmlns="urn:HPD_IncidentInterface_WS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AuthenticationInfo"><userName>SECRETUSER</userName><password>SECRETPASSWORD</password></HelpDesk_QueryList_Service></soap:Body></soap:Envelope> > {noformat} > I've also tried 9.0.0.Alpha1 with same result. What could be wrong? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3987) Regression regarding WS Client when using header authentication

by Vlastimil Eliáš (JIRA)

[ https://issues.jboss.org/browse/WFLY-3987?page=com.atlassian.jira.plugin.... ] Vlastimil Eliáš updated WFLY-3987: ---------------------------------- Attachment: (was: Jboss Soap.txt) > Regression regarding WS Client when using header authentication > --------------------------------------------------------------- > > Key: WFLY-3987 > URL: https://issues.jboss.org/browse/WFLY-3987 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.1.0.Final, 9.0.0.Alpha1 > Environment: Linux (Ubuntu 14.04), OpenJDK 1.7.0_65, Wildfly 8.0/8.1/9.0A > Reporter: Marcus Carlson > Assignee: Alessio Soldano > Attachments: HPD_IncidentInterface_Create_WS.wsdl, Tomcat.txt > > > I'm trying to integrate a Web Service client based on BMC Remedy product where Web service authentication is handled in Soap Header and not basic authentication. See AuthenticationInfo element on https://github.com/macmorning/itsm_mobileview/blob/master/SoapUI%20Projec... for an example of how the WSDL file looks like. > I've enabled Xadditionalheaders so I get the AuthenticationInfo as the last argument, like this: > {noformat} > port.helpDeskQueryListService(qualification, startRecord, maxLimit, authInfo); > {noformat} > Problem is that this was working fine in WildFly 8.0 generating the following SOAP Request: > {noformat} > ID: 1 > Address: https://SERVER/arsys/services/ARService?server=SERVER&webService=HPD_Inci... > Encoding: UTF-8 > Http-Method: POST > Content-Type: text/xml > Headers: {Accept=[*/*], SOAPAction=["urn:HPD_IncidentInterface_WS/HelpDesk_QueryList_Service"]} > Payload: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><AuthenticationInfo xmlns="urn:HPD_IncidentInterface_WS"><userName>SECRETUSER</userName><password>SECRETPASSWORD</password></AuthenticationInfo></soap:Header><soap:Body><HelpDesk_QueryList_Service xmlns="urn:HPD_IncidentInterface_WS"><Qualification>'Status' = "Closed"</Qualification><startRecord>0</startRecord><maxLimit>1000</maxLimit></HelpDesk_QueryList_Service></soap:Body></soap:Envelope> > {noformat} > With 8.1 it's generating a completly different payload with the Header element in Body and body completly missing (!): > {noformat} > ID: 2 > Address: https://SERVER/arsys/services/ARService?server=SERVER&webService=HPD_Inci... > Encoding: UTF-8 > Http-Method: POST > Content-Type: text/xml > Headers: {Accept=[*/*], SOAPAction=["urn:HPD_IncidentInterface_WS/HelpDesk_QueryList_Service"]} > Payload: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><HelpDesk_QueryList_Service xmlns="urn:HPD_IncidentInterface_WS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AuthenticationInfo"><userName>SECRETUSER</userName><password>SECRETPASSWORD</password></HelpDesk_QueryList_Service></soap:Body></soap:Envelope> > {noformat} > I've also tried 9.0.0.Alpha1 with same result. What could be wrong? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1745) An error occurs when we add a new Drools runtime

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1745?page=com.atlassian.jira.plugi... ] Andrej Podhradsky reassigned DROOLS-1745: ----------------------------------------- Assignee: (was: Robert (Bob) Brodt) > An error occurs when we add a new Drools runtime > ------------------------------------------------ > > Key: DROOLS-1745 > URL: https://issues.jboss.org/browse/DROOLS-1745 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: Devstudio 11.1.0.AM2 + Devstudio IS 11.1.0.AM1-SNAPSHOT > Drools plugin 7.3.0.Final > BRMS 6.4.4.GA > Reporter: Andrej Podhradsky > Attachments: errorLog.txt > > > The following error occurs when we add a new Drools runtime > {code} > The Runtime at '/home/apodhrad/Projects/server-installer/brms-6.4.4.GA/target/jboss-brms-6.4-engine' may have more than one version of installed jar files for the drools product. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1745) An error occurs when we add a new Drools runtime

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created DROOLS-1745: ----------------------------------------- Summary: An error occurs when we add a new Drools runtime Key: DROOLS-1745 URL: https://issues.jboss.org/browse/DROOLS-1745 Project: Drools Issue Type: Bug Components: eclipse plugin Affects Versions: 7.3.0.Final Environment: Devstudio 11.1.0.AM2 + Devstudio IS 11.1.0.AM1-SNAPSHOT Drools plugin 7.3.0.Final BRMS 6.4.4.GA Reporter: Andrej Podhradsky Assignee: Robert (Bob) Brodt Attachments: errorLog.txt The following error occurs when we add a new Drools runtime {code} The Runtime at '/home/apodhrad/Projects/server-installer/brms-6.4.4.GA/target/jboss-brms-6.4-engine' may have more than one version of installed jar files for the drools product. {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1651) FEEL String marshaller fails on list of null

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1651?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1651: ---------------------------------- Fix Version/s: 7.4.0.Final > FEEL String marshaller fails on list of null > -------------------------------------------- > > Key: DROOLS-1651 > URL: https://issues.jboss.org/browse/DROOLS-1651 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Mélanie Gauthier > Assignee: Fedor Gavrilov > Fix For: 7.4.0.Final > > Attachments: Invalid function.dmn > > > For example, if you execute the invalid attached file (kind attribute of the function isn't right - it is set to undefined) it produces an array of null. > When calling FEELStringMarshaller.INSTANCE.marshall(decisionResult.getResult()) you get a NPE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1672) "not" in variable name doesn't work

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1672?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1672: ---------------------------------- Fix Version/s: (was: 7.4.0.Final) > "not" in variable name doesn't work > ----------------------------------- > > Key: DROOLS-1672 > URL: https://issues.jboss.org/browse/DROOLS-1672 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Labels: reported-by-qe > > When trying this test case: > {code}{ is not exactly 18 : != 18, bob is not exactly 18 : is not exactly 18(16) }.bob is not exactly 18"{code} > the parser fails like this [1] > [1] https://gist.github.com/baldimir/7c13b9c76087d44f95802ded8b72877f > Will provide a PR with a reproducer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1663: ---------------------------------- Fix Version/s: (was: 7.4.0.Final) > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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