October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3124) Nested GridCell/GridCellValue

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3124?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3124: --------------------------------- Tester: Klara Kufova Labels: ScenarioSimulation (was: ) > Nested GridCell/GridCellValue > ----------------------------- > > Key: DROOLS-3124 > URL: https://issues.jboss.org/browse/DROOLS-3124 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: Screenshot from 2018-10-12 10-10-01.png > > > For some click/double click combination (not easy to reproduce) inside a gridcell, it seems that a nested GridCell or gridcellvallue will be created: > in the screenshot it is shown by the empty box inside the cell below do2.mydo1.myint1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3112) FEEL Compiler: modularize FEELImpl compiler/interpreter vs. DMNFEELHelper

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3112?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3112: ----------------------------------- Sprint: 2018 Week 42-44 > FEEL Compiler: modularize FEELImpl compiler/interpreter vs. DMNFEELHelper > -------------------------------------------------------------------------- > > Key: DROOLS-3112 > URL: https://issues.jboss.org/browse/DROOLS-3112 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Code in FEELImpl could be reused in the DMNFEELHelper, but it cannot be shared, because FEELImpl exposes an interface to evaluate expressions, while DMNFEELHelper needs access to the compiler backend. > Solution: separate the compilation pipeline and the interpreter pipeline from the public FEEL interface to promote code reuse. In particular, CompilerBytecodeLoader can be probably split between some kind of CompiledUnit+CompiledUnaryTest impls that provide methods to retrieve Java source code and/or JVM bytecode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2924) Factor out Unit behavior to allow pluggable backends

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-2924?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-2924: ----------------------------------- Description: The way (Rule) units are scheduled into execution is ad-hoc for Rule Units. Assuming we want to generalize the "Unit" flow of execution to a global API, having e.g. - rule units (Drools) - process units (jBPM) - etc. then the mechanism must allow for extensions. This tasks consists in implementing a more general "Scheduler" interface, to which units can be submitted. The scheduler decides which unit has to be run next, depending on which Units are "in scope" and the actions they perform (e.g., submitting new units for run()'ing, registering a guard, etc.) was: e.g.: - rule units (Drools) - process units (jBPM) etc. > Factor out Unit behavior to allow pluggable backends > ---------------------------------------------------- > > Key: DROOLS-2924 > URL: https://issues.jboss.org/browse/DROOLS-2924 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: Stunner, drools-core > > The way (Rule) units are scheduled into execution is ad-hoc for Rule Units. Assuming we want to generalize the "Unit" flow of execution to a global API, having e.g. > - rule units (Drools) > - process units (jBPM) > - etc. > then the mechanism must allow for extensions. > This tasks consists in implementing a more general "Scheduler" interface, to which units can be submitted. The scheduler decides which unit has to be run next, depending on which Units are "in scope" and the actions they perform (e.g., submitting new units for run()'ing, registering a guard, etc.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3064) POJO Unification

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3064?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3064: ----------------------------------- Sprint: 2018 Week 39-41 (was: 2018 Week 39-41, 2018 Week 42-44) > POJO Unification > ----------------- > > Key: DROOLS-3064 > URL: https://issues.jboss.org/browse/DROOLS-3064 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > implement a general algorithm for recursive unification of POJO structures -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2924) Factor out Unit behavior to allow pluggable backends

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-2924?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-2924: ----------------------------------- Sprint: 2018 Week 33-35, 2018 Week 42-44 (was: 2018 Week 33-35) > Factor out Unit behavior to allow pluggable backends > ---------------------------------------------------- > > Key: DROOLS-2924 > URL: https://issues.jboss.org/browse/DROOLS-2924 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: Stunner, drools-core > > The way (Rule) units are scheduled into execution is ad-hoc for Rule Units. Assuming we want to generalize the "Unit" flow of execution to a global API, having e.g. > - rule units (Drools) > - process units (jBPM) > - etc. > then the mechanism must allow for extensions. > This tasks consists in implementing a more general "Scheduler" interface, to which units can be submitted. The scheduler decides which unit has to be run next, depending on which Units are "in scope" and the actions they perform (e.g., submitting new units for run()'ing, registering a guard, etc.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2924) Factor out Unit behavior to allow pluggable backends

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-2924?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-2924: ----------------------------------- Labels: Stunner drools-core (was: Stunner) > Factor out Unit behavior to allow pluggable backends > ---------------------------------------------------- > > Key: DROOLS-2924 > URL: https://issues.jboss.org/browse/DROOLS-2924 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: Stunner, drools-core > > e.g.: > - rule units (Drools) > - process units (jBPM) > etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4083) org.apache.httpcomponents.core requires org.apache.commons.codec

by Sanne Grinovero (Jira)

[ https://issues.jboss.org/browse/WFCORE-4083?page=com.atlassian.jira.plugi... ] Sanne Grinovero reassigned WFCORE-4083: --------------------------------------- Assignee: Sanne Grinovero > org.apache.httpcomponents.core requires org.apache.commons.codec > ---------------------------------------------------------------- > > Key: WFCORE-4083 > URL: https://issues.jboss.org/browse/WFCORE-4083 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 6.0.1.Final > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Major > Fix For: 7.0.0.Alpha1 > > > In WildFly 14 we get: > {code:java} > Exception in thread "Hibernate Search: Elasticsearch transport thread-2" java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64 > 2018-09-03 11:58:13,120 ERROR [stderr] (Hibernate Search: Elasticsearch transport thread-2) at org.apache.http.impl.auth.BasicScheme.authenticate(BasicScheme.java:168) > 2018-09-03 11:58:13,120 ERROR [stderr] (Hibernate Search: Elasticsearch transport thread-2) at org.apache.http.impl.auth.HttpAuthenticator.doAuth(HttpAuthenticator.java:239) > 2018-09-03 11:58:13,120 ERROR [stderr] (Hibernate Search: Elasticsearch transport thread-2) at org.apache.http.impl.auth.HttpAuthenticator.generateAuthResponse(HttpAuthenticator.java:218) > 2018-09-03 11:58:13,120 ERROR [stderr] (Hibernate Search: Elasticsearch transport thread-2) at org.apache.http.impl.nio.client.MainClientExec.generateRequest(MainClientExec.java:224) > {code} > Seems that the *org.apache.httpcomponents.core* (WildFly core) module is not declaring the dependency on module *org.apache.commons.codec* (WildFly full). > Should this be added as an optional dependency, or maybe the need for this module warrants moving the *org.apache.commons.codec* module to WildFly core ? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3132) DMN assign null to ItemDefinition with allowedValues

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3132?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3132: ----------------------------------- Sprint: 2018 Week 39-41, 2018 Week 42-44 (was: 2018 Week 39-41) > DMN assign null to ItemDefinition with allowedValues > ---------------------------------------------------- > > Key: DROOLS-3132 > URL: https://issues.jboss.org/browse/DROOLS-3132 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: image-2018-10-12-21-56-28-776.png > > > Currently engine allow to assign null to ItemDefinition with allowedValues. > But DMN spec mentions: > !image-2018-10-12-21-56-28-776.png! > So assigning null to ItemDefinition with allowedValues(not expliciting null) should raise a typeCheck error, either when assigned to InputData, either when assigned to a DRGElement(Decision), with such typeRef. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3067: ----------------------------------- Sprint: 2018 Week 39-41, 2018 Week 42-44 (was: 2018 Week 39-41) > [DMN Designer] Automatic Layout Feature Workbench Integration > ------------------------------------------------------------- > > Key: DROOLS-3067 > URL: https://issues.jboss.org/browse/DROOLS-3067 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, Screenshot from 2018-10-10 08-22-25.png, a3.dmn, auto.png, manual.png > > > Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature. > h2. Acceptance tests > # -User is prompted if he wants or not to apply autolayout feature- discussed in comments > # Positioning is automatically stored after model opening (/) > # Simple graph, no branches, starting node -> node -> ...... node -> ending node (/) > # Tree, top node in the middle of the screen, some branches to all sides (/) > # Graph with big crossing of edges, similar to complete graph (/) > # Large (but sparse) graph, not all nodes visible without scrolling (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3024: ----------------------------------- Sprint: 2018 Week 39-41, 2018 Week 42-44 (was: 2018 Week 39-41) > [DMN Designer] Data Types - Add nested data types > ------------------------------------------------- > > Key: DROOLS-3024 > URL: https://issues.jboss.org/browse/DROOLS-3024 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, options.png > > > - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu: > !options.png|thumbnail! > h2. Manual Acceptance Test > h3. Insert above > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > - no warning in browser console (/) > h3. Insert below > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > h3. Insert nested > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > h3. Build and deploy > - Build and deploy model that uses new created data type (x) > -- DROOLS-3110 > -- DROOLS-3111 -- This message was sent by Atlassian Jira (v7.12.1#712002)

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