January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4905) [DMN Designer] Code Completion - Index all elements named by users

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4905?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4905: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Code Completion - Index all elements named by users > ------------------------------------------------------------------ > > Key: DROOLS-4905 > URL: https://issues.redhat.com/browse/DROOLS-4905 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Create the infrastructure code that provided all elements named by the user. It will be called by the suggestion component. So users will be able to see as suggestions DRG Elements and Data Types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12998) MicroProfile OpenAPI: validate generated OpenAPI document

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-12998?page=com.atlassian.jira.plugi... ] Fabio Burzigotti moved WFWIP-292 to WFLY-12998: ----------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-12998 (was: WFWIP-292) Component/s: MP OpenAPI (was: MP OpenAPI) > MicroProfile OpenAPI: validate generated OpenAPI document > ----------------------------------------------------------- > > Key: WFLY-12998 > URL: https://issues.redhat.com/browse/WFLY-12998 > Project: WildFly > Issue Type: Enhancement > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Major > > Currently no validation is provided for generated document and actually the spec is not requesting for vendors to do that [1] but it would definitely be a key improvement for customers and users in general to know that the generated document is checked and appropriate action is taken in case content is not valid (e.g.: log WARN messages etc.). > Online Swagger Editor [2] was used to verify that non valid content was generated. > Also it should be evaluated whether to mention this behavior in community or product docs. > [1] > https://download.eclipse.org/microprofile/microprofile-open-api-1.1.2/mic... > [2] > https://editor.swagger.io/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4950: ------------------------------------ [~jomarko] Now I understood, thank you, I was looking only the second row :) > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1921) [GSS][7.2.2] HTTP External Security Not Supported by Elytron

by Ashley Abdel-Sayed (Jira)

Ashley Abdel-Sayed created ELY-1921: --------------------------------------- Summary: [GSS][7.2.2] HTTP External Security Not Supported by Elytron Key: ELY-1921 URL: https://issues.redhat.com/browse/ELY-1921 Project: WildFly Elytron Issue Type: Requirement Affects Versions: 1.11.0.Final Reporter: Ashley Abdel-Sayed Assignee: Ashley Abdel-Sayed For legacy security, there's an EXTERNAL HTTP authentication mechanism (io.undertow.security.impl.ExternalAuthenticationMechanism) which performs no verification and simply uses the principal that was passed from the REMOTE_USER attribute by the AJP protocol. There is a "ClientLoginModule" in legacy security used as such: https://access.redhat.com/solutions/3465231. It is a requirement to add an equivalent of this EXTERNAL mechanism available in legacy and Elytron-SASL for Elytron-HTTP in order to migrate away from legacy security. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12997) Upgrade jboss-ejb-client from 4.0.28.Final to ...

by Tomas Hofman (Jira)

[ https://issues.redhat.com/browse/WFLY-12997?page=com.atlassian.jira.plugi... ] Tomas Hofman moved JBEAP-18529 to WFLY-12997: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12997 (was: JBEAP-18529) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Fix Version/s: (was: 7.3.1.GA) > Upgrade jboss-ejb-client from 4.0.28.Final to ... > ------------------------------------------------- > > Key: WFLY-12997 > URL: https://issues.redhat.com/browse/WFLY-12997 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Tomas Hofman > Assignee: Ilia Vassilev > Priority: Major > > https://github.com/wildfly/jboss-ejb-client -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12980) Full reload is needed after microprofile-jwt-smallrye subsystem removal

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12980?page=com.atlassian.jira.plugi... ] Bartosz Baranowski commented on WFLY-12980: ------------------------------------------- [~jkasik] & [~dlofthouse] - given above can this one be rejected? I dont think there is anything we can do about this. Any change to classloading/processors etc require :reload (unless change are scoped to deployment, IIRC?) > Full reload is needed after microprofile-jwt-smallrye subsystem removal > ----------------------------------------------------------------------- > > Key: WFLY-12980 > URL: https://issues.redhat.com/browse/WFLY-12980 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Priority: Major > > When user is removing MP subsystem, full reload is required. This is partly a benefit because it provides a fast fail solution for deployments which requires classes from this subsystem. On the other hand, reload might not be feasible for user under in their current conditions. This is why it has to be reduced as much as possible. > Is there other way to provide fast fail without requiring full reload? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4950: ------------------------------------- Please compare EXPECTED column in first and second row [~yamer] > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4870) Materialize consequences using Drools

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4870?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4870: -------------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Materialize consequences using Drools > ------------------------------------- > > Key: DROOLS-4870 > URL: https://issues.redhat.com/browse/DROOLS-4870 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Major > > Currently consequences using Drools are not materialized (extracted in a different lambda) because they are capturing, as they use the relative bitmask instance. > We should find a way to pass the bitmask instance to the consequence so that we can materialize them. > This means we should probably not change only the compiler, but also the interpreter of the DSL -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4922) LinkageError: attempted duplicate class definition for materialized Lambda during incremental compilation

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4922?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4922: -------------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > LinkageError: attempted duplicate class definition for materialized Lambda during incremental compilation > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4922 > URL: https://issues.redhat.com/browse/DROOLS-4922 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > In case of incremental compilation, say, a rule is changed: > - A lambda consequence (or a lambda predicate) has the same expression > - But an "import" statement is added to the rule > It will results in > {noformat} > [ERROR] testIdenticalConsequenceButImportChange[PATTERN_DSL](org.drools.modelcompiler.IncrementalCompilationTest) Time elapsed: 3.135 s <<< ERROR! > java.lang.LinkageError: loader org.drools.dynamic.DynamicProjectClassLoader$DefaultInternalTypesClassLoader @2b0dc227 (instance of org.drools.dynamic.DynamicProjectClassLoader$DefaultInternalTypesClassLoader, child of 'app' jdk.internal.loader.ClassLoaders$AppClassLoader) attempted duplicate class definition for org.drools.test.LambdaConsequence6F5B5EC739B778AE0EE14FA22BAFE144. > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:877) > at org.drools.dynamic.DynamicProjectClassLoader$DefaultInternalTypesClassLoader.defineClass(DynamicProjectClassLoader.java:97) > at org.drools.reflective.classloader.ProjectClassLoader.defineType(ProjectClassLoader.java:183) > at org.drools.reflective.classloader.ProjectClassLoader.defineClass(ProjectClassLoader.java:195) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.reinitModifiedClasses(KieContainerImpl.java:323) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:243) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:236) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.updateToVersion(KieContainerImpl.java:194) > at org.drools.modelcompiler.IncrementalCompilationTest.testIdenticalConsequenceButImportChange(IncrementalCompilationTest.java:257) > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4561) DMN introspect PMML for output types

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4561?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4561: -------------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > DMN introspect PMML for output types > ------------------------------------ > > Key: DROOLS-4561 > URL: https://issues.redhat.com/browse/DROOLS-4561 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Toshiya Kobayashi > Priority: Critical > Labels: good-first-issue > > Currently PMML is introspected for input parameters names and types. > Also for output parameters names. > Currently the feature is missing PMML introspection for output parameters types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 January 2020