April 2019 - jboss-jira - Jboss List Archives

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

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3702: ----------------------------------- Tester: Jozef Marko > [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, drools-tools > Fix For: 7.21.0.Final > > Attachments: auto-magnets.gif, fixed-magnets.gif, 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11116: ------------------------------------- {quote}I will set passivation to false and test.{quote} Don't do that. passivation=true will evict bean instances from memory to disk when the max-entries threshold is exceeded. Disabling passivation will force the bean to persist to a file on every invocation. If you don't want passivation, remove the file-store altogether. > Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception) > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11116 > URL: https://issues.jboss.org/browse/WFLY-11116 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final, 15.0.0.Final > Reporter: ziad saade > Assignee: Paul Ferraro > Priority: Critical > > I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow: > > Book.java > TestBean testBean=null; > if(session.getAttribute("testBean")!=null) > testBean = (TestBean)session.getAttribute("testBean"); > else{ > testBean=new TestBean(); > session.setAttribute("testBean",testBean); > } > testBean.setAmount("10"); > > response.sendRedirect("BookPreview"); > > > The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated. > > BookPreview.java > > TestBean testBean = (TestBean)session.getAttribute("testBean"); > String amount = testBean.getAmount; //Null pointer exception when submitting the form > > <form method="Post" action="BookPreview"> > > </form> > > TestBean.java > > public class TestBean implements java.io.Serializable { > > private static final long serialVersionUID = 1L; > private String amount; > > public String getAmount() { > return amount; > } > > public void setAmount(String amount) { > this.amount = amount; > } > } > > Kindly advice how to fix the problem at the level of the server configuration. > PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....) > > Thanks and Best Regards -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3884) Prepare a Drools on Quarkus presentation

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3884?page=com.atlassian.jira.plugi... ] Mario Fusco moved RHDM-922 to DROOLS-3884: ------------------------------------------ Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-3884 (was: RHDM-922) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW QE Status: NEW > Prepare a Drools on Quarkus presentation > ---------------------------------------- > > Key: DROOLS-3884 > URL: https://issues.jboss.org/browse/DROOLS-3884 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-713) There is too many jenkins slaves

by Filip Brychta (Jira)

Filip Brychta created SWSQE-713: ----------------------------------- Summary: There is too many jenkins slaves Key: SWSQE-713 URL: https://issues.jboss.org/browse/SWSQE-713 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta There are multiple jenkins slaves started for one jenkins job. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3865) Document internal flow

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3865?page=com.atlassian.jira.plugi... ] Massimiliano Dessi commented on DROOLS-3865: -------------------------------------------- https://github.com/desmax74/openshift-hacep/tree/master/img > Document internal flow > ---------------------- > > Key: DROOLS-3865 > URL: https://issues.jboss.org/browse/DROOLS-3865 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3865) Document internal flow

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3865?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-3865. ---------------------------------------- Resolution: Done > Document internal flow > ---------------------- > > Key: DROOLS-3865 > URL: https://issues.jboss.org/browse/DROOLS-3865 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3831) [DMN Designer] Included Models - Create a service for providing information about external DMN models

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3831?page=com.atlassian.jira.plugi... ] Guilherme Gomes reassigned DROOLS-3831: --------------------------------------- Assignee: Guilherme Gomes (was: Daniel José dos Santos) > [DMN Designer] Included Models - Create a service for providing information about external DMN models > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-3831 > URL: https://issues.jboss.org/browse/DROOLS-3831 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Create the {{ExternalDMNModelsService}} service for providing information about external DMN files. > This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11985) Upgrade commons-codec from 1.10 to 1.11

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-11985?page=com.atlassian.jira.plugin... ] Ilia Vassilev updated WFLY-11985: --------------------------------- Security: (was: Red Hat Internal) > Upgrade commons-codec from 1.10 to 1.11 > --------------------------------------- > > Key: WFLY-11985 > URL: https://issues.jboss.org/browse/WFLY-11985 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Affects Versions: 16.0.0.Final > Reporter: Ilia Vassilev > Assignee: James Perkins > Priority: Critical > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-155) WildFly gets stuck with TLSv1.3 on JDK 11

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFWIP-155?page=com.atlassian.jira.plugin.... ] Jan Stourac resolved WFWIP-155. ------------------------------- Resolution: Done I have tried this with build based on: * https://github.com/fjuma/wildfly-elytron/tree/ELY-1706 * https://github.com/fjuma/wildfly-core/tree/WFCORE-4172 ** rebased against current WildFly-Core master 245593b472abf284bbeefb4f46c7170b7651e65d ** XNIO 3.7.1.Final utilized ** Undertow 2.0.20.Final utilized * WildFly branch used - current master 2ee5a9937eda7bd39878df9e5dad1181fb57ab2e, with aforementioned wildfly-core build. I can see WildFly to no more stuck with TLSv1.3 following 'steps to reproduce'. Resolving this. [~adamkrajcik], raise your voice if you have any objections. > WildFly gets stuck with TLSv1.3 on JDK 11 > ----------------------------------------- > > Key: WFWIP-155 > URL: https://issues.jboss.org/browse/WFWIP-155 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Environment: JDK 11 > Reporter: Adam Krajcik > Assignee: Farah Juma > Priority: Blocker > Labels: jdk11 > > WildFly gets stuck with when using TLSv1.3. The process starts to heavily use the processor and cannot be stopped by simple SIGINT(Ctrl+C). The issue needs further investigation as no apparent reason for it being stuck. > One possibility is mentioned in the comments for UNDERTOW-1493 is [JDK-8208526|https://bugs.openjdk.java.net/browse/JDK-8208526]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3883) Add running indicator during test scenario execution

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-3883: ------------------------------------- Summary: Add running indicator during test scenario execution Key: DROOLS-3883 URL: https://issues.jboss.org/browse/DROOLS-3883 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca When user runs a test there is no indicator while it runs -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 April 2019