June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5397) Data object containing at least one enum fails to be opend in Data model editor

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-5397?page=com.atlassian.jira.plug... ] Anna Dupliak closed DROOLS-5397. -------------------------------- Resolution: Done Could not reproduce anymore > Data object containing at least one enum fails to be opend in Data model editor > ------------------------------------------------------------------------------- > > Key: DROOLS-5397 > URL: https://issues.redhat.com/browse/DROOLS-5397 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation > Attachments: EnumFieldOnlyObject.java, EnumTest.java, model view with enum types.webm > > > It is possible to manage enum types in scenario simulation to do so in Rule based test scenario it is possible to have data object enum. But including at least one field that implements Enumeration interface breaks the model editor and fails to show fields on the UI See: [^model view with enum types.webm] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1979) Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1979?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on ELY-1979: --------------------------------------- Elytron requires Java 11 to build so as you say looks like it should just be a case of adding the missing methods and passing then through to a delegate when appropriate. We don't expect users of these classes to access them using any approach other than the standard API they expose so as for example SSLEngine doesn't contain those methods on the older releases if anyone bypasses that it will be expected to fail. > Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package > --------------------------------------------------------------------------- > > Key: ELY-1979 > URL: https://issues.redhat.com/browse/ELY-1979 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.12.0.Final > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.12.1.CR1 > > > JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new methods to some of the javax.net.ssl classes that elytron wraps in org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and SSLSocket classes (plus various non-javax classes.) > If Elytron were to require 251 or later to build perhaps this could be a simple matter of adding new methods to the wrappers and calling the delegate, under the expectation that at runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could use reflection and throw a UOE if the methods are not available. > [1] https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm... > [2] https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5402) [Scesim Editor] Fit error reason to the popup

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-5402: ------------------------------------ Summary: [Scesim Editor] Fit error reason to the popup Key: DROOLS-5402 URL: https://issues.redhat.com/browse/DROOLS-5402 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Affects Versions: 7.38.0.Final Reporter: Anna Dupliak Assignee: Daniele Zonca Attachments: image-2020-06-03-09-20-34-662.png When package name is long then error reason gets out of the inline section of the popup !image-2020-06-03-09-20-34-662.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1979) Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1979?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1979: ---------------------------------- Fix Version/s: 1.12.1.CR1 > Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package > --------------------------------------------------------------------------- > > Key: ELY-1979 > URL: https://issues.redhat.com/browse/ELY-1979 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.12.0.Final > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.12.1.CR1 > > > JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new methods to some of the javax.net.ssl classes that elytron wraps in org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and SSLSocket classes (plus various non-javax classes.) > If Elytron were to require 251 or later to build perhaps this could be a simple matter of adding new methods to the wrappers and calling the delegate, under the expectation that at runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could use reflection and throw a UOE if the methods are not available. > [1] https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm... > [2] https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1979) Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1979?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned ELY-1979: ------------------------------------- Assignee: Darran Lofthouse > Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package > --------------------------------------------------------------------------- > > Key: ELY-1979 > URL: https://issues.redhat.com/browse/ELY-1979 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.12.0.Final > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Blocker > > JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new methods to some of the javax.net.ssl classes that elytron wraps in org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and SSLSocket classes (plus various non-javax classes.) > If Elytron were to require 251 or later to build perhaps this could be a simple matter of adding new methods to the wrappers and calling the delegate, under the expectation that at runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could use reflection and throw a UOE if the methods are not available. > [1] https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm... > [2] https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2481) Use IdentityHashmap in Util.TYPES and ClassConfigurator

by Bela Ban (Jira)

Bela Ban created JGRP-2481: ------------------------------ Summary: Use IdentityHashmap in Util.TYPES and ClassConfigurator Key: JGRP-2481 URL: https://issues.redhat.com/browse/JGRP-2481 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0.0.Beta2 When we have lookup hashmaps, populated at startup, and not changed afterwards, we can use IdentityHashmaps, as a {{get()}} is constant. For keys with a contiguous range (e.g. {{[1 .. 20]}}), we might even use a simple array of keys and values, e.g. {{[K1,V1,K2,V2, ... Kn,Vn}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2480) ObjectMessage: better marshalling

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2480?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2480. ---------------------------- Resolution: Done > ObjectMessage: better marshalling > --------------------------------- > > Key: JGRP-2480 > URL: https://issues.redhat.com/browse/JGRP-2480 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Beta2 > > > Currently, {{ObjectMessage}} accepts only objects of type {{SizeStreamable}} and wraps everything else into {{ObjectWrapper}} instances. > This means that primitive types (e.g. "{{7}}" or "{{hello world}}") will be wrapped, too. The disadvantage of {{ObjectWrapper}} is that it performs _eager marshalling_, creating an unwanted byte[] array before the message is actually marshalled. On the receiver side, another byte[] array will be created before the actual unmarshalling starts. > Solution: accept primitive types (e.g. {{int}}, {{Integer}}, {{String}}, {{AsciiString}}, {{byte[]}} etc) directly, without wrapping them into an {{ObjectWrapper}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5400) Executable model build fails with SerialVersionUID and key annotations

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5400?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5400: -------------------------------- Sprint: 2020 Week 22-24 (from May 25) > Executable model build fails with SerialVersionUID and key annotations > ---------------------------------------------------------------------- > > Key: DROOLS-5400 > URL: https://issues.redhat.com/browse/DROOLS-5400 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.38.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Minor > Attachments: serial-version-uid-exec-model.zip > > > Executable model compilation fails on declared types with both _@SerialVersionUID_ and _@key_ annotations. > Example of DRL that fails to compile: > {noformat} > declare ServiceInformation > @serialVersionUID( 0 ) > code: String @key > end > rule "create new ServiceInformation" > when > then > insert( new ServiceInformation("123456") ); > end > {noformat} > Error: > {noformat} > Error Messages: > Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=null, line=56, column=0 > text=Duplicate method ServiceInformation(String) in type ServiceInformation] > Message [id=2, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=null, line=61, column=0 > text=Duplicate method ServiceInformation(String) in type ServiceInformation] > {noformat} > The example works fine when compiling without executable model. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5401) Suppress RuntimeException in ExecModelLambdaPostProcessor

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5401?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5401: -------------------------------------- Description: When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda (don't want to break a build). Currently ExecModelLambdaPostProcessor throws RuntimeException only in unusual cases but still it's better to log and return rather than throwing RuntimeException. Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346). was: When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda. Currently ExecModelLambdaPostProcessor throws RuntimeException only in unusual cases but still it's better to log and return rather than throwing RuntimeException. Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346). > Suppress RuntimeException in ExecModelLambdaPostProcessor > --------------------------------------------------------- > > Key: DROOLS-5401 > URL: https://issues.redhat.com/browse/DROOLS-5401 > Project: Drools > Issue Type: Enhancement > Components: executable model > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to non-externalized lambda (don't want to break a build). Currently ExecModelLambdaPostProcessor throws RuntimeException only in unusual cases but still it's better to log and return rather than throwing RuntimeException. > Btw, we can detect non-externalized lambda with option "drools.check.nonExternalisedLambda" (DROOLS-5346). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3746) JavaScript run error when edit Guided Decision Tables on latest chrome

by Sergey Manukyan (Jira)

[ https://issues.redhat.com/browse/DROOLS-3746?page=com.atlassian.jira.plug... ] Sergey Manukyan edited comment on DROOLS-3746 at 6/3/20 12:13 AM: ------------------------------------------------------------------ Had same issue, appeared next day suddenly, was using OSX, OpenJDK 1.8, the Decision Manager 7.7. on EAP 7.2 . Same issue on Chrome 83 & Firefox 68 {quote} 15:03:03,651 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-41) Error from user: dmAdmin Error ID: -79860134 Location: LibraryPerspective|$ProjectScreen,GuidedDecisionTableEditor?path_uri=default://master@MySpace/AAAPricing/src/main/resources/com/myspace/aaapricing/Pricing%2520Table.gdst&file_name=Pricing%20Table.gdst&has_version_support=true Exception: Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/decision-central/verifier/dtableVerifier/3EA3E9D35E...) {quote} The workaround with {{-Dorg.kie.verification.disable-dtable-realtime-verification=true}} helped was (Author: smanukya): Had same issue, appeared next day suddenly, was using OSX, OpenJDK 1.8, the Decision Manager 7.7. on EAP 7.2 {quote} 15:03:03,651 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-41) Error from user: dmAdmin Error ID: -79860134 Location: LibraryPerspective|$ProjectScreen,GuidedDecisionTableEditor?path_uri=default://master@MySpace/AAAPricing/src/main/resources/com/myspace/aaapricing/Pricing%2520Table.gdst&file_name=Pricing%20Table.gdst&has_version_support=true Exception: Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://localhost:8080/decision-central/verifier/dtableVerifier/3EA3E9D35E...) {quote} The workaround with {{-Dorg.kie.verification.disable-dtable-realtime-verification=true}} helped > JavaScript run error when edit Guided Decision Tables on latest chrome > ---------------------------------------------------------------------- > > Key: DROOLS-3746 > URL: https://issues.redhat.com/browse/DROOLS-3746 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.18.0.Final > Reporter: xiaodong zhang > Assignee: Toni Rikkola > Priority: Blocker > > When updated to the latest chrome (72.0.3626.121), When I do edit using Guided Decision Tables, an error will throw. > The error detail is : > | Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://127.0.0.1:8080/kie-drools-wb/verifier/dtableVerifier/C1C6DDEF649DA...) > My version is 7.14.0.Final and I also tried the latest 7.18.0.Final but no lucky. It's happend on both windows and Mac client when using the latest chrome or safari. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 June 2020