April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3816) Investigate Github branch source plugin for Submarine PR checks

by Tibor Zimanyi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3816?page=com.atlassian.jira.plugi... ] Tibor Zimanyi updated DROOLS-3816: ---------------------------------- Labels: submarine (was: ) > Investigate Github branch source plugin for Submarine PR checks > --------------------------------------------------------------- > > Key: DROOLS-3816 > URL: https://issues.jboss.org/browse/DROOLS-3816 > Project: Drools > Issue Type: Task > Components: build > Affects Versions: 7.19.0.Final > Reporter: Tibor Zimanyi > Assignee: Tibor Zimanyi > Priority: Major > Labels: submarine > Fix For: 8.0.0.Final > > > PR automation needs to be prepared for the Submarine initiative repositories. There is a suggestion from [~manaRH] to take a look at Github Branch Source plugin [1] as it should be the recommended way how to do this. > Deliverables: > - PR automation proof of concept for the submarine engines repository. > [1] https://go.cloudbees.com/docs/plugins/github-branch-source/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3702) [Stunner] Arrows are incorrectly positioned when save-open diagram

by Kirill Gaevskii (Jira)

[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ] Kirill Gaevskii commented on DROOLS-3702: ----------------------------------------- Hi [~roger600], issue mentioned by you looks different. I think DMN editor is not preserving sequence flows position after save/reopen. In BPMN Designer it affects only Preview panel and always, no need to save and reopen. > [Stunner] Arrows are incorrectly positioned when save-open diagram > ------------------------------------------------------------------ > > Key: DROOLS-3702 > URL: https://issues.jboss.org/browse/DROOLS-3702 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: Stunner > Attachments: process-designer-connectors-magnets-issues.png, weird_arrow.gif > > > 1. Add a `Decision Node` > 2. Add a `Input Data Node` bellow `Decision Node` > 3. Connect `Input Data Node` to `Decision Node` > 4. Save > 5. Close > 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned. > I noticed this in DMN Showcase and in drools-wb. > And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3811) Refactor expression evaluator for Rule and DMN

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3811?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3811: ---------------------------------- Story Points: 1 > Refactor expression evaluator for Rule and DMN > ---------------------------------------------- > > Key: DROOLS-3811 > URL: https://issues.jboss.org/browse/DROOLS-3811 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Minor > Labels: ScenarioSimulation > > Rename methods and tests in both expression evaluator as follow: > - evaluate -> evaluateUnaryExpression > - getValueForGiven -> evaluateLiteralExpression -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3811) Refactor expression evaluator for Rule and DMN

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3811?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3811: ---------------------------------- Sprint: 2019 Week 14-16 > Refactor expression evaluator for Rule and DMN > ---------------------------------------------- > > Key: DROOLS-3811 > URL: https://issues.jboss.org/browse/DROOLS-3811 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Minor > Labels: ScenarioSimulation > > Rename methods and tests in both expression evaluator as follow: > - evaluate -> evaluateUnaryExpression > - getValueForGiven -> evaluateLiteralExpression -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3702) [Stunner] Arrows are incorrectly positioned when save-open diagram

by Kirill Gaevskii (Jira)

[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ] Kirill Gaevskii reassigned DROOLS-3702: --------------------------------------- Assignee: Michael Anstis (was: Roger Martinez) > [Stunner] Arrows are incorrectly positioned when save-open diagram > ------------------------------------------------------------------ > > Key: DROOLS-3702 > URL: https://issues.jboss.org/browse/DROOLS-3702 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: Stunner > Attachments: process-designer-connectors-magnets-issues.png, weird_arrow.gif > > > 1. Add a `Decision Node` > 2. Add a `Input Data Node` bellow `Decision Node` > 3. Connect `Input Data Node` to `Decision Node` > 4. Save > 5. Close > 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned. > I noticed this in DMN Showcase and in drools-wb. > And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3730) Add support to DMN constraints on inputs (report input validation errors)

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3730?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3730: --------------------------------------- UPDATE: As discussed with [~tari_manga] we are going to evaluate two different approaches: - Enrich DMN input Maps to contains all the expected fields considering each DMN Type (with `null` values) - Add a "light" type check directly in the engine like the current one but without the enforcing on the structure of the type (= if the field exists it should be correct otherwise no error) > Add support to DMN constraints on inputs (report input validation errors) > ------------------------------------------------------------------------- > > Key: DROOLS-3730 > URL: https://issues.jboss.org/browse/DROOLS-3730 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > See this example https://github.com/kiegroup/drools/compare/master...tarilabs:tarilabs-201... > and try with a value out of the domain ranga [0..100]. > when a Decision or any evaluation which depends on such InputData is triggered, an error message like the following is reported > ```Error while evaluating node 'my decision' for dependency 'my input': the dependency value '999' is not allowed by the declared type (DMNType{ http://www.trisotech.com/definitions/_7ab67159-21c7-4985-91fc-f0d0174898db : tNumber0100 })``` -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka commented on WFLY-11858: ----------------------------------------- [~rakcheru] we already made the release of Narayana `5.9.5.Final` with the fix and the PR for the component in the new version being involved is created for WildFly (WFLY-11917). WildFly release is done quarterly (http://lists.jboss.org/pipermail/wildfly-dev/2017-December/006250.html) and micro releases are done only in case of some blocker issue. I assume you would need take the WFLY16 and update the Narayana there or wait for the WFLY17 to be released (I expect the WFLY-11917 will be merged till that time). > [Wildfly16] CDI fails to inject InitialContext during startup > ------------------------------------------------------------- > > Key: WFLY-11858 > URL: https://issues.jboss.org/browse/WFLY-11858 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Final > Reporter: Rakesh Cherukuri > Assignee: Matěj Novotný > Priority: Major > Attachments: stacktrace.log > > > We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error > _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_ > In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error. > Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself. > Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :) > Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3818) Assign a complex type object to a property with modified label leads to NPE

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3818?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-3818: ------------------------------- Description: Steps to reproduce it: - Open a new scenario asset - Assign a instance (eg . Author) - Rename it (eg. Author_test) - Try to assign a Complex type as a property (eg. a Collection) - A NPE is thown. > Assign a complex type object to a property with modified label leads to NPE > --------------------------------------------------------------------------- > > Key: DROOLS-3818 > URL: https://issues.jboss.org/browse/DROOLS-3818 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation > > Steps to reproduce it: > - Open a new scenario asset > - Assign a instance (eg . Author) > - Rename it (eg. Author_test) > - Try to assign a Complex type as a property (eg. a Collection) > - A NPE is thown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

by Rakesh Cherukuri (Jira)

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Rakesh Cherukuri commented on WFLY-11858: ----------------------------------------- [~ochaloup][~manovotn][~ljnelson][~mkouba] Thanks for all your timely contribution. Tested WildFly16-with-the-fix and the server is starting up just fine. No failures out of 50 times. What is the plan for the fix ? Will there be a WildFlyv16.0.1 ? > [Wildfly16] CDI fails to inject InitialContext during startup > ------------------------------------------------------------- > > Key: WFLY-11858 > URL: https://issues.jboss.org/browse/WFLY-11858 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Final > Reporter: Rakesh Cherukuri > Assignee: Matěj Novotný > Priority: Major > Attachments: stacktrace.log > > > We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error > _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_ > In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error. > Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself. > Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :) > Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3147) [DMN Designer] Keyboard shortcuts

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3147?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3147: -------------------------------- Description: The DMN and Scenario Simulation editors should support keyboard shortcuts (similar for current GDT tables) for basic operations like: Navigation between cells Invoking inline context menu Start Editing cell Finish editing Cell This support is crucial for integration selenium testing. In the DMN the selenium testing wouldn't be possible without the Navigation Dock (BAPL-966). was: The DMN editor should support keyboard shortcuts (similar for current GDT tables) for basic operations like editing of DRD elements. This support is crucial for integration selenium testing. In integration test we are able to select node on canvas thanks to Navigation Dock (BAPL-966). Once element is selected we need shortcuts for: - Appending element - Morphing element - Renaming element Thanks to Navigation Dock (BAPL-966) we are also able to open Context Editor (where applicable). In Context editor we need shortcuts for: - Navigation between cells - Invoking inline context menu - Navigate in inline context menu - Select item in inline context menu - Start Editing cell - Finish editing Cell - Cancel editing Cell > [DMN Designer] Keyboard shortcuts > --------------------------------- > > Key: DROOLS-3147 > URL: https://issues.jboss.org/browse/DROOLS-3147 > Project: Drools > Issue Type: Epic > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Minor > Labels: drools-tools, reported-by-qe > > The DMN and Scenario Simulation editors should support keyboard shortcuts (similar for current GDT tables) for basic operations like: > Navigation between cells > Invoking inline context menu > Start Editing cell > Finish editing Cell > This support is crucial for integration selenium testing. In the DMN the selenium testing wouldn't be possible without the Navigation Dock (BAPL-966). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 2019