July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12191) StackOverflowError is thrown when invoking a REST end-point, with ClientRequestFilter/ClientResponseFilter registered

by Deny Wuysan (Jira)

[ https://issues.jboss.org/browse/WFLY-12191?page=com.atlassian.jira.plugin... ] Deny Wuysan commented on WFLY-12191: ------------------------------------ Also, I am currently using ClientRequestFilter/Response to login/logout when calling a REST end-point, which is sitting behind a form-based authentication (i.e. j_security_check, j_username, j_password). To be honest, I am not sure if this is commonly done (or even if this is a good practice), since I haven't found any examples on the net. I wonder how they secure REST end-points which is also a Java EE web application. Any pointer/guidance will be much appreciated. > StackOverflowError is thrown when invoking a REST end-point, with ClientRequestFilter/ClientResponseFilter registered > --------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12191 > URL: https://issues.jboss.org/browse/WFLY-12191 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 17.0.0.Final > Environment: Fedora 30, Oracle JDK 1.8.0_181 > Reporter: Deny Wuysan > Assignee: Alessio Soldano > Priority: Major > Attachments: Authenticator.java, BatchManager.java, WFLY-12191.zip > > > Please find attached the two Java files corresponding to the error. When setting debugger on line 50 for Authenticator.java, notice repetitive calls occurred, ONLY on Wildfly 17.0.0.Final. > Have re-tested this case on Wildfly 16.0.0.Final and the REST call made successfully. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12191) StackOverflowError is thrown when invoking a REST end-point, with ClientRequestFilter/ClientResponseFilter registered

by Deny Wuysan (Jira)

[ https://issues.jboss.org/browse/WFLY-12191?page=com.atlassian.jira.plugin... ] Deny Wuysan commented on WFLY-12191: ------------------------------------ *I have verified by removing @Provider on authenticator, and it works!* Having said that, referring to Java EE Spec, for ClientRequestFilter, which states: _"An extension interface implemented by client request filters. Filters implementing this interface MUST be annotated with @Provider. This type of filters is supported only as part of the Client API."_ https://docs.oracle.com/javaee/7/api/javax/ws/rs/client/ClientRequestFilt... ... so I assume this is a bug which will be addressed in the future release of Wildfly? > StackOverflowError is thrown when invoking a REST end-point, with ClientRequestFilter/ClientResponseFilter registered > --------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12191 > URL: https://issues.jboss.org/browse/WFLY-12191 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 17.0.0.Final > Environment: Fedora 30, Oracle JDK 1.8.0_181 > Reporter: Deny Wuysan > Assignee: Alessio Soldano > Priority: Major > Attachments: Authenticator.java, BatchManager.java, WFLY-12191.zip > > > Please find attached the two Java files corresponding to the error. When setting debugger on line 50 for Authenticator.java, notice repetitive calls occurred, ONLY on Wildfly 17.0.0.Final. > Have re-tested this case on Wildfly 16.0.0.Final and the REST call made successfully. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4296) Rewrite parsing of modified properties

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4296: ------------------------------------ Summary: Rewrite parsing of modified properties Key: DROOLS-4296 URL: https://issues.jboss.org/browse/DROOLS-4296 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Luca Molteni See Consequence::findModifiedProperties Currently modified properties are parsed throughout the consequence, but that information is already present after the preprocessing of the ModifyStatement so it can be simplified a lot. This can be forward ported to Kogito also -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4294) Inside DROOLS-WB, replace IllegalTransitive rule with dependency:analyze-only

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4294?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-4294: ------------------------------------- Summary: Inside DROOLS-WB, replace IllegalTransitive rule with dependency:analyze-only (was: Replace IllegalTransitive rule with dependency:analyze-only) > Inside DROOLS-WB, replace IllegalTransitive rule with dependency:analyze-only > ----------------------------------------------------------------------------- > > Key: DROOLS-4294 > URL: https://issues.jboss.org/browse/DROOLS-4294 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Scope of this PR is to replace usage of IllegalTransitive rule with dependency:analyze-only plugin/goal (https://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-moj...). > Some clean-up of unused/declared dependencies will also be done (*not* in the drools-wb-webapp) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4294) Replace IllegalTransitive rule with dependency:analyze-only

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4294: ---------------------------------------- Summary: Replace IllegalTransitive rule with dependency:analyze-only Key: DROOLS-4294 URL: https://issues.jboss.org/browse/DROOLS-4294 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Scope of this PR is to replace usage of IllegalTransitive rule with dependency:analyze-only plugin/goal (https://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-moj...). Some clean-up of unused/declared dependencies will also be done (*not* in the drools-wb-webapp) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4293) IncrementalRuleCodegen should generate all related rules when one DRL file is changed

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4293: -------------------------------------- Summary: IncrementalRuleCodegen should generate all related rules when one DRL file is changed Key: DROOLS-4293 URL: https://issues.jboss.org/browse/DROOLS-4293 Project: Drools Issue Type: Task Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. Solution: we allow to codegen all the related files when compilation is re-triggered. The solution entails reworking IncrementalRuleCodegen -- with the occasion, we will be able to refactor so that this class is used everywhere rule codegen is done (including maven plugin and tests) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4256) IncrementalRuleCodegen should generate all related rules when one DRL file is changed

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4256?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4256: ----------------------------------- Description: At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. Solution: we allow to codegen all the related files when compilation is re-triggered. The solution entails reworking IncrementalRuleCodegen -- with the occasion, we will be able to refactor so that this class is used everywhere rule codegen is done. was: At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. Solution: we allow to codegen all the related files when compilation is re-triggered. The solution entails reworking > IncrementalRuleCodegen should generate all related rules when one DRL file is changed > ------------------------------------------------------------------------------------- > > Key: DROOLS-4256 > URL: https://issues.jboss.org/browse/DROOLS-4256 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Edoardo Vacchi > Priority: Major > > At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. > Solution: we allow to codegen all the related files when compilation is re-triggered. The solution entails reworking IncrementalRuleCodegen -- with the occasion, we will be able to refactor so that this class is used everywhere rule codegen is done. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4256) IncrementalRuleCodegen should generate all related rules when one DRL file is changed

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4256?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4256: ----------------------------------- Description: At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. Solution: we allow to codegen all the related files when compilation is re-triggered. The solution entails reworking IncrementalRuleCodegen -- with the occasion, we will be able to refactor so that this class is used everywhere rule codegen is done (including maven plugin and tests) was: At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. Solution: we allow to codegen all the related files when compilation is re-triggered. The solution entails reworking IncrementalRuleCodegen -- with the occasion, we will be able to refactor so that this class is used everywhere rule codegen is done. > IncrementalRuleCodegen should generate all related rules when one DRL file is changed > ------------------------------------------------------------------------------------- > > Key: DROOLS-4256 > URL: https://issues.jboss.org/browse/DROOLS-4256 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Edoardo Vacchi > Priority: Major > > At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. > Solution: we allow to codegen all the related files when compilation is re-triggered. The solution entails reworking IncrementalRuleCodegen -- with the occasion, we will be able to refactor so that this class is used everywhere rule codegen is done (including maven plugin and tests) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4256) IncrementalRuleCodegen should generate all related rules when one DRL file is changed

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4256?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4256: ----------------------------------- Summary: IncrementalRuleCodegen should generate all related rules when one DRL file is changed (was: Make Quarkus extension hot reload to also work with new rules) > IncrementalRuleCodegen should generate all related rules when one DRL file is changed > ------------------------------------------------------------------------------------- > > Key: DROOLS-4256 > URL: https://issues.jboss.org/browse/DROOLS-4256 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Edoardo Vacchi > Priority: Major > > At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4256) IncrementalRuleCodegen should generate all related rules when one DRL file is changed

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4256?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4256: ----------------------------------- Description: At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. Solution: we allow to codegen all the related files when compilation is re-triggered. The solution entails reworking was:At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. > IncrementalRuleCodegen should generate all related rules when one DRL file is changed > ------------------------------------------------------------------------------------- > > Key: DROOLS-4256 > URL: https://issues.jboss.org/browse/DROOLS-4256 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Edoardo Vacchi > Priority: Major > > At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. > Solution: we allow to codegen all the related files when compilation is re-triggered. The solution entails reworking -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 July 2019