August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1609) Augment FEEL AST node at compilation with return type

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1609?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1609: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31) > Augment FEEL AST node at compilation with return type > ----------------------------------------------------- > > Key: DROOLS-1609 > URL: https://issues.jboss.org/browse/DROOLS-1609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > This is needed so to be able to determine the result of a boxed function at compile time, in turn to be able at compile time to determine a valid compilation without error of a BKM for instance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

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

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1651?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1651: ----------------------------------- Sprint: 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33 (was: 2017 Week 28-29, 2017 Week 30-31) > 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: Edson Tirelli > 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, 10 months

1
0
0 / 0

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

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1672?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1672: ----------------------------------- Sprint: 2017 Week 30-31, 2017 Week 32-33 (was: 2017 Week 30-31) > "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 > Fix For: 7.2.0.Final > > > When trying this test case: > { is not exactly 18 : != 18, bob is not exactly 18 : is not exactly 18(16) }.bob is not exactly 18" > 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, 10 months

1
0
0 / 0

[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 (was: 2017 Week 30-31) > 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: Edson Tirelli > Fix For: 7.2.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, 10 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 (was: 2017 Week 22-23, 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31) > 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.2.0.Final > > > Write the documentation for both FEEL and DMN engines. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31) > 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.2.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, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1153) Elytron: problem with Maven dependencies

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/ELY-1153?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned ELY-1153: -------------------------------- Assignee: Tomaz Cerar (was: Darran Lofthouse) > Elytron: problem with Maven dependencies > ---------------------------------------- > > Key: ELY-1153 > URL: https://issues.jboss.org/browse/ELY-1153 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.CR4 > Reporter: Josef Cacek > Assignee: Tomaz Cerar > Priority: Critical > > Majority of Elytron Maven dependencies have scope {{provided}}. It means they are not included when Elytron is used as a project dependency (e.g. together with EJB) and compilation fails. > We need either to make them {{compile}} scoped or provide an additional Elytron BOM package so users have a simple way for Elytron usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1153) Elytron: problem with Maven dependencies

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/ELY-1153?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated ELY-1153: ----------------------------- Affects Version/s: 1.1.0.CR4 > Elytron: problem with Maven dependencies > ---------------------------------------- > > Key: ELY-1153 > URL: https://issues.jboss.org/browse/ELY-1153 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.CR4 > Reporter: Josef Cacek > Assignee: Tomaz Cerar > Priority: Critical > > Majority of Elytron Maven dependencies have scope {{provided}}. It means they are not included when Elytron is used as a project dependency (e.g. together with EJB) and compilation fails. > We need either to make them {{compile}} scoped or provide an additional Elytron BOM package so users have a simple way for Elytron usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9195) Quickstart guide: helloworld is not working

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9195?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-9195: ----------------------------------- Quickstarts in 11.x branch are "dev" ones, and need documentation to be build (processed) first to be 100% consumable. I will create 11.0.0.Beta1 tag and do proper release with all documentation & htmls to fix all this. > Quickstart guide: helloworld is not working > ------------------------------------------- > > Key: WFLY-9195 > URL: https://issues.jboss.org/browse/WFLY-9195 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 11.0.0.Beta1 > Reporter: Julien Dore > Assignee: Tomaz Cerar > Priority: Minor > > I'm following the [quickstart guide|https://github.com/wildfly/quickstart/blob/10.x/guide/HelloworldQui...] and i have downloaded the quickstart-11.x. > With my wildfly server running i'm launching (from quickstart-11.x/helloworld): > {code:java} > package wildfly:deploy > {code} > as describe in the doc but this fail with the following stack: > {code:java} > [ERROR] No plugin found for prefix 'wildfly' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\PC\.m2\repository), jboss-enterprise-maven-repository (https://maven.repository.redhat.com/ga/), jboss-enterprise-maven-repository-ea (https://maven.repository.redhat.com/earlyaccess/all/), jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/), central (https://repo.maven.apache.org/maven2)] -> [Help 1] > {code} > Adding the following code in pom.xml solve the issue: > {code:java} > <plugin> > <groupId>org.wildfly.plugins</groupId> > <artifactId>wildfly-maven-plugin</artifactId> > <version>1.1.0.Final</version> > </plugin> > {code} > Note that the application is then accessible at _http://localhost:8080/helloworld/HelloWorld_ and not _http://localhost:8080/wildfly-helloworld/HelloWorld_ as written in the documentation. > Note also that these links are not working: > * Installing and starting the JBoss server on Linux, Unix or Mac OS X > * Installing and starting the JBoss server on Windows -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9195) Quickstart guide: helloworld is not working

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9195?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-9195: ------------------------------ Estimated Difficulty: Medium (was: Low) > Quickstart guide: helloworld is not working > ------------------------------------------- > > Key: WFLY-9195 > URL: https://issues.jboss.org/browse/WFLY-9195 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 11.0.0.Beta1 > Reporter: Julien Dore > Assignee: Tomaz Cerar > Priority: Minor > > I'm following the [quickstart guide|https://github.com/wildfly/quickstart/blob/10.x/guide/HelloworldQui...] and i have downloaded the quickstart-11.x. > With my wildfly server running i'm launching (from quickstart-11.x/helloworld): > {code:java} > package wildfly:deploy > {code} > as describe in the doc but this fail with the following stack: > {code:java} > [ERROR] No plugin found for prefix 'wildfly' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\PC\.m2\repository), jboss-enterprise-maven-repository (https://maven.repository.redhat.com/ga/), jboss-enterprise-maven-repository-ea (https://maven.repository.redhat.com/earlyaccess/all/), jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/), central (https://repo.maven.apache.org/maven2)] -> [Help 1] > {code} > Adding the following code in pom.xml solve the issue: > {code:java} > <plugin> > <groupId>org.wildfly.plugins</groupId> > <artifactId>wildfly-maven-plugin</artifactId> > <version>1.1.0.Final</version> > </plugin> > {code} > Note that the application is then accessible at _http://localhost:8080/helloworld/HelloWorld_ and not _http://localhost:8080/wildfly-helloworld/HelloWorld_ as written in the documentation. > Note also that these links are not working: > * Installing and starting the JBoss server on Linux, Unix or Mac OS X > * Installing and starting the JBoss server on Windows -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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