April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11870) abstract classes with @EJB annotation included in libraries will cause deployment failures

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-11870?page=com.atlassian.jira.plugin... ] Tomas Hofman reassigned WFLY-11870: ----------------------------------- Assignee: Tomas Hofman (was: Brian Stansberry) > abstract classes with @EJB annotation included in libraries will cause deployment failures > ------------------------------------------------------------------------------------------ > > Key: WFLY-11870 > URL: https://issues.jboss.org/browse/WFLY-11870 > Project: WildFly > Issue Type: Bug > Components: EJB, Server > Reporter: Wolf-Dieter Fink > Assignee: Tomas Hofman > Priority: Major > Labels: Regression, deployment, injection > Attachments: ReproducerInjection.zip > > > If an archive include libraries with interfaces and abstract classes the deployment will fail if there are annotations for injection like @EJB. > Only if the injected EJB is available within the deployed file (or any other deployment) it is possible to deploy it. > As the abstract class can not cause any instance the failure does not make sense. > Also former versions are deploying the same file correct and work fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3837) Typos in DSL Editor screenshot

by Vidya Iyengar (Jira)

Vidya Iyengar created DROOLS-3837: ------------------------------------- Summary: Typos in DSL Editor screenshot Key: DROOLS-3837 URL: https://issues.jboss.org/browse/DROOLS-3837 Project: Drools Issue Type: Bug Reporter: Vidya Iyengar Assignee: Mario Fusco Details here: https://issues.jboss.org/browse/BXMSDOC-3864 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[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: ---------------------------------- Fix Version/s: 8.0.0.Final > 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)

6 years, 6 months

1
0
0 / 0

[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)

6 years, 6 months

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)

6 years, 6 months

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)

6 years, 6 months

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)

6 years, 6 months

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)

6 years, 6 months

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)

6 years, 6 months

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)

6 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019