August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10801) Upgrade ASM to 6.2.1

by Kabir Khan (JIRA)

Kabir Khan created WFLY-10801: --------------------------------- Summary: Upgrade ASM to 6.2.1 Key: WFLY-10801 URL: https://issues.jboss.org/browse/WFLY-10801 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate, Web Services Reporter: Kabir Khan Assignee: Kabir Khan In https://github.com/wildfly/wildfly/pull/11490#issuecomment-410845864 it was found that ASM 6.0 does not work on Java 10. The PR passes with ASM 6.2.1. The other main user is CXF and [~jim.ma] reports: {quote} CXF master has already upgraded ASM to 6.2, that implies it won't be problem to upgrade from 6.0 to 6.2.1 in Wildfly. {quote} CC [~asoldano] [~ropalka][~jamezp][~smarlow] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2838) Avoid using readAccessor in alpha network compiler

by Luca Molteni (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2838?page=com.atlassian.jira.plugi... ] Luca Molteni reassigned DROOLS-2838: ------------------------------------ Assignee: Luca Molteni (was: Mario Fusco) > Avoid using readAccessor in alpha network compiler > -------------------------------------------------- > > Key: DROOLS-2838 > URL: https://issues.jboss.org/browse/DROOLS-2838 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > > Alpha Network compiler should be limited to the executable model so that we can avoid using the readAccessor and use a LambdaAccessor instead -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2835) NPE While using incremental compilation

by Luca Molteni (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2835?page=com.atlassian.jira.plugi... ] Luca Molteni reassigned DROOLS-2835: ------------------------------------ Assignee: Luca Molteni (was: Mario Fusco) > NPE While using incremental compilation > --------------------------------------- > > Key: DROOLS-2835 > URL: https://issues.jboss.org/browse/DROOLS-2835 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Luca Molteni > > IncrementalCompilationCepTest.testUpdateWithDeclarationPresent:312 » NullPointer > IncrementalCompilationTest.testDeclaredTypeInDifferentPackage:3262->doFire:3307 » NullPointer > IncrementalCompilationTest.testDeletedFile:306 » NullPointer > IncrementalCompilationTest.testKJarUpgradeWithNewRuleAndStatelessSession:3905 » NullPointer > IncrementalCompilationTest.testKJarUpgradeWithNewRule:3849 » NullPointer -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2836) Support compiling of a Big Rule

by Luca Molteni (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2836?page=com.atlassian.jira.plugi... ] Luca Molteni reassigned DROOLS-2836: ------------------------------------ Assignee: Luca Molteni (was: Mario Fusco) > Support compiling of a Big Rule > ------------------------------- > > Key: DROOLS-2836 > URL: https://issues.jboss.org/browse/DROOLS-2836 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Luca Molteni > > RemoveRuleTest.testRemoveBigRule > java.lang.RuntimeException: This is a bug. Please contact the development team: > [org/drools/core/reteoo/compiled/Compiledorg_drools_compiler_test_SimpleFactNetwork8aecdf1db7f9b4f4abcbafdd301c63d7c.java (6279:25) : package org.drools.compiler.test does not exist, org/drools/core/reteoo/compiled/Compiledorg_drools_compiler_test_SimpleFactNetwork8aecdf1db7f9b4f4abcbafdd301c63d7c.java (6279:69) : package org.drools.compiler.test does not exist, org/drools/core/reteoo/compiled/Compiledorg_drools_compiler_test_SimpleFactNetwork8aecdf1db7f9b4f4abcbafdd301c63d7c.java (7899:25) : package org.drools.compiler.test does not exist, org/drools/core/reteoo/compiled/Compiledorg_drools_compiler_test_SimpleFactNetwork8aecdf1db7f9b4f4abcbafdd301c63d7c.java (7899:69) : package org.drools.compiler.test does not exist] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2845) Extend the existing verifier to support DMN tables

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2845?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2845: --------------------------------- Summary: Extend the existing verifier to support DMN tables (was: Extend the existing verfier to support DMN tables) > Extend the existing verifier to support DMN tables > -------------------------------------------------- > > Key: DROOLS-2845 > URL: https://issues.jboss.org/browse/DROOLS-2845 > Project: Drools > Issue Type: Epic > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Labels: drools-tools > > h1. Goal > Reuse the V&V created for Guided Decision Tables on the DMN tables. > h1. Workload divided to steps > I propose the work goes in the following steps. After each step I should be able to merge into master. > Steps: > # Move Verifier core to kie-wb-common > # Move V&V reporting UI to kie-wb-common > # Make the web worker connector reusable for different V&V types > # Make a servlet module for DMN that allows the download of the Web Worker. > # Create an adapter for DMN tables > # Add support for ranges ( these are given in DMN so no need to use JSR303 ) > # Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense > h1. Time and risks > h2. #1, #2, #3, #4 and #7 moving, copying code or doing refactoring > Most of the work items are just about moving, copying code or doing refactoring. These are easy to estimate and I think they are doable in one sprint along with everything else I do. Already started few of these so it is easier for me to estimate how long they take. > h2. 5. Create an adapter for DMN tables > Adapters job is to take the model ( DMN or dtable ) and tear it down into smaller bits that the Verifier actually inspects. The core Verifier basically only sees rules or rows as collections of conditions and actions. This is why I feel once the adapter is done, the verifier will automatically work for DMN tables. This adapter also keeps track of the cell to action/condition connections. > This area is where most of the work is that is hard to estimate, since there is some unknowns here. In theory DMN adapter is a lot easier to do than the DTable adapter was. Due to the unknown I will have to say 3 weeks. > h2. 6. Add support for ranges > Mario helped to get the range checks in order. The V&V now works with unlimited ranges, but adding known range limitation is in a way just about adding in the data of a mock rule that checks for the area that is outside of the range. I’ll play it safe here and say one week, but at the moment this feels really easy. > h1. Just to make it clear > This work only targets the DMN table in the similar format that it is in the Guided Decision Table. So it does not cover a Verification of the entire DMN diagram that can have several tables that possibly complete each other. We have the same situation if we have multiple DRL Tables in a ksession. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2853) Make DMN Verifier use the experimental tag

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-2853: ------------------------------------ Summary: Make DMN Verifier use the experimental tag Key: DROOLS-2853 URL: https://issues.jboss.org/browse/DROOLS-2853 Project: Drools Issue Type: Feature Request Components: DMN Editor, verifier Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2851) DMN Verifier: Add support for ranges ( these are given in DMN so no need to use JSR303 )

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2851?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2851: -------------------------------- Tester: Jozef Marko Labels: drools-tools (was: ) > DMN Verifier: Add support for ranges ( these are given in DMN so no need to use JSR303 ) > ---------------------------------------------------------------------------------------- > > Key: DROOLS-2851 > URL: https://issues.jboss.org/browse/DROOLS-2851 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Labels: drools-tools > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2852) Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2852?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2852: -------------------------------- Tester: Jozef Marko Labels: drools-tools (was: ) > Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense > ----------------------------------------------------------------------------------- > > Key: DROOLS-2852 > URL: https://issues.jboss.org/browse/DROOLS-2852 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Labels: drools-tools > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3996) GC logging is not working on Java 9

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3996?page=com.atlassian.jira.plugi... ] Rostislav Svoboda moved WFLY-10091 to WFCORE-3996: -------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3996 (was: WFLY-10091) Component/s: Scripts (was: Scripts) > GC logging is not working on Java 9 > ----------------------------------- > > Key: WFCORE-3996 > URL: https://issues.jboss.org/browse/WFCORE-3996 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Rostislav Svoboda > Assignee: Radovan Stancel > Priority: Blocker > Labels: Java11, blocker-WF14 > > GC logging is not working on Java 9. This is related to the fact G1 GC is default and there are changes in configuration option. > {code} > GC_LOG="true" ./standalone.sh > {code} > Java 8: > {code} > JAVA_OPTS: -server -verbose:gc -Xloggc:"/Users/rsvoboda/TESTING/7.2.0.CD12.CR1/jboss-eap-7.2/standalone/log/gc.log" > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 > -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M > -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > {code} > Java 9: > {code} > JAVA_OPTS: -server -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m > -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2845) Extend the existing verfier to support DMN tables

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2845?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2845: --------------------------------- Description: h1. Goal Reuse the V&V created for Guided Decision Tables on the DMN tables. h1. Workload divided to steps I propose the work goes in the following steps. After each step I should be able to merge into master. Steps: # Move Verifier core to kie-wb-common # Move V&V reporting UI to kie-wb-common # Make the web worker connector reusable for different V&V types # Make a servlet module for DMN that allows the download of the Web Worker. # Create an adapter for DMN tables # Add support for ranges ( these are given in DMN so no need to use JSR303 ) # Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense h1. Time and risks h2. #1, #2, #3, #4 and #7 moving, copying code or doing refactoring Most of the work items are just about moving, copying code or doing refactoring. These are easy to estimate and I think they are doable in one sprint along with everything else I do. Already started few of these so it is easier for me to estimate how long they take. h2. 5. Create an adapter for DMN tables Adapters job is to take the model ( DMN or dtable ) and tear it down into smaller bits that the Verifier actually inspects. The core Verifier basically only sees rules or rows as collections of conditions and actions. This is why I feel once the adapter is done, the verifier will automatically work for DMN tables. This adapter also keeps track of the cell to action/condition connections. This area is where most of the work is that is hard to estimate, since there is some unknowns here. In theory DMN adapter is a lot easier to do than the DTable adapter was. Due to the unknown I will have to say 3 weeks. h2. 6. Add support for ranges Mario helped to get the range checks in order. The V&V now works with unlimited ranges, but adding known range limitation is in a way just about adding in the data of a mock rule that checks for the area that is outside of the range. I’ll play it safe here and say one week, but at the moment this feels really easy. h1. Just to make it clear This work only targets the DMN table in the similar format that it is in the Guided Decision Table. So it does not cover a Verification of the entire DMN diagram that can have several tables that possibly complete each other. We have the same situation if we have multiple DRL Tables in a ksession. > Extend the existing verfier to support DMN tables > ------------------------------------------------- > > Key: DROOLS-2845 > URL: https://issues.jboss.org/browse/DROOLS-2845 > Project: Drools > Issue Type: Epic > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Labels: drools-tools > > h1. Goal > Reuse the V&V created for Guided Decision Tables on the DMN tables. > h1. Workload divided to steps > I propose the work goes in the following steps. After each step I should be able to merge into master. > Steps: > # Move Verifier core to kie-wb-common > # Move V&V reporting UI to kie-wb-common > # Make the web worker connector reusable for different V&V types > # Make a servlet module for DMN that allows the download of the Web Worker. > # Create an adapter for DMN tables > # Add support for ranges ( these are given in DMN so no need to use JSR303 ) > # Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense > h1. Time and risks > h2. #1, #2, #3, #4 and #7 moving, copying code or doing refactoring > Most of the work items are just about moving, copying code or doing refactoring. These are easy to estimate and I think they are doable in one sprint along with everything else I do. Already started few of these so it is easier for me to estimate how long they take. > h2. 5. Create an adapter for DMN tables > Adapters job is to take the model ( DMN or dtable ) and tear it down into smaller bits that the Verifier actually inspects. The core Verifier basically only sees rules or rows as collections of conditions and actions. This is why I feel once the adapter is done, the verifier will automatically work for DMN tables. This adapter also keeps track of the cell to action/condition connections. > This area is where most of the work is that is hard to estimate, since there is some unknowns here. In theory DMN adapter is a lot easier to do than the DTable adapter was. Due to the unknown I will have to say 3 weeks. > h2. 6. Add support for ranges > Mario helped to get the range checks in order. The V&V now works with unlimited ranges, but adding known range limitation is in a way just about adding in the data of a mock rule that checks for the area that is outside of the range. I’ll play it safe here and say one week, but at the moment this feels really easy. > h1. Just to make it clear > This work only targets the DMN table in the similar format that it is in the Guided Decision Table. So it does not cover a Verification of the entire DMN diagram that can have several tables that possibly complete each other. We have the same situation if we have multiple DRL Tables in a ksession. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 2018