February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13164) When "corrupted" public key is supplied to server, user is not informed

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFLY-13164?page=com.atlassian.jira.plugi... ] Jan Kasik updated WFLY-13164: ----------------------------- Priority: Blocker (was: Major) > When "corrupted" public key is supplied to server, user is not informed > ----------------------------------------------------------------------- > > Key: WFLY-13164 > URL: https://issues.redhat.com/browse/WFLY-13164 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Affects Versions: 19.0.0.Beta2, 20.0.0.Beta1 > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Blocker > Attachments: CorruptedKeyTest.war > > > When corrupted public key (a valid key cannot be extracted from the string value) is supplied to JWT verifier, user is not informed since there is no error message in log and clients receives 401 status code in response instead of an error code of 500. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13164) When "corrupted" public key is supplied to server, user is not informed

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFLY-13164?page=com.atlassian.jira.plugi... ] Jan Kasik commented on WFLY-13164: ---------------------------------- Raising priority to blocker since this issue is a regression when compared against state when the feature was being merged. > When "corrupted" public key is supplied to server, user is not informed > ----------------------------------------------------------------------- > > Key: WFLY-13164 > URL: https://issues.redhat.com/browse/WFLY-13164 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Affects Versions: 19.0.0.Beta2, 20.0.0.Beta1 > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Blocker > Attachments: CorruptedKeyTest.war > > > When corrupted public key (a valid key cannot be extracted from the string value) is supplied to JWT verifier, user is not informed since there is no error message in log and clients receives 401 status code in response instead of an error code of 500. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13164) When "corrupted" public key is supplied to server, user is not informed

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFLY-13164?page=com.atlassian.jira.plugi... ] Jan Kasik updated WFLY-13164: ----------------------------- Affects Version/s: 20.0.0.Beta1 > When "corrupted" public key is supplied to server, user is not informed > ----------------------------------------------------------------------- > > Key: WFLY-13164 > URL: https://issues.redhat.com/browse/WFLY-13164 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Affects Versions: 19.0.0.Beta2, 20.0.0.Beta1 > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Major > Attachments: CorruptedKeyTest.war > > > When corrupted public key (a valid key cannot be extracted from the string value) is supplied to JWT verifier, user is not informed since there is no error message in log and clients receives 401 status code in response instead of an error code of 500. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13165) When "corrupted" public key is supplied to server, user is not informed

by Jan Kasik (Jira)

Jan Kasik created WFLY-13165: -------------------------------- Summary: When "corrupted" public key is supplied to server, user is not informed Key: WFLY-13165 URL: https://issues.redhat.com/browse/WFLY-13165 Project: WildFly Issue Type: Bug Components: MP JWT Affects Versions: 19.0.0.Beta2 Reporter: Jan Kasik Assignee: Darran Lofthouse When corrupted public key (a valid key cannot be extracted from the string value) is supplied to JWT verifier, user is not informed since there is no error message in log and clients receives 401 status code in response instead of an error code of 500. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13165) When "corrupted" public key is supplied to server, user is not informed

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFLY-13165?page=com.atlassian.jira.plugi... ] Jan Kasik deleted WFLY-13165: ----------------------------- > When "corrupted" public key is supplied to server, user is not informed > ----------------------------------------------------------------------- > > Key: WFLY-13165 > URL: https://issues.redhat.com/browse/WFLY-13165 > Project: WildFly > Issue Type: Bug > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Major > > When corrupted public key (a valid key cannot be extracted from the string value) is supplied to JWT verifier, user is not informed since there is no error message in log and clients receives 401 status code in response instead of an error code of 500. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13164) When "corrupted" public key is supplied to server, user is not informed

by Jan Kasik (Jira)

Jan Kasik created WFLY-13164: -------------------------------- Summary: When "corrupted" public key is supplied to server, user is not informed Key: WFLY-13164 URL: https://issues.redhat.com/browse/WFLY-13164 Project: WildFly Issue Type: Bug Components: MP JWT Affects Versions: 19.0.0.Beta2 Reporter: Jan Kasik Assignee: Darran Lofthouse Attachments: CorruptedKeyTest.war When corrupted public key (a valid key cannot be extracted from the string value) is supplied to JWT verifier, user is not informed since there is no error message in log and clients receives 401 status code in response instead of an error code of 500. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5060) [DMN Designer] Editor allows node with prefix/trailing space

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5060?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5060: -------------------------------- Description: I understand [DROOLS-5017] has been re-purposed to allow Info and Warn level messages be displayed on Stunner Validation dialog. That is fine. But, imho, an UX point is not being considered, where is necessary instead. By the DMN spec, a node should not have a prefix/trailing space, as space insensitivity would mandate 1 trailing or 2 trailing spaces are simply ignored etc. The engine is lenient to avoid this crashing the evaluation, but still is a bad designed model to persist the node name (DRGElement name and its corresponding variable name) with those extra spaces IMHO. Further, I consider is just the Analyst which slipped a space. In my perspective, the editor should just strip away the prefix/trailing space: * -While Importing a DMN model from file Upload- (See [DROOLS-5062|https://issues.redhat.com/browse/DROOLS-5062]) * While editing a DRGElement and hitting OK to save its name For your consideration, thanks. h2. Manual acceptance test - Rename a node, check undo/redo - Rename node as ctrl-c/ctrl+v - Try to use \tab in the middle of the name - Leading space - Trailing space - Save and reopen - Documentation tab - Rename via node popup - Rename via properties panel - Rename via expression grid - where applicable was: I understand [DROOLS-5017] has been re-purposed to allow Info and Warn level messages be displayed on Stunner Validation dialog. That is fine. But, imho, an UX point is not being considered, where is necessary instead. By the DMN spec, a node should not have a prefix/trailing space, as space insensitivity would mandate 1 trailing or 2 trailing spaces are simply ignored etc. The engine is lenient to avoid this crashing the evaluation, but still is a bad designed model to persist the node name (DRGElement name and its corresponding variable name) with those extra spaces IMHO. Further, I consider is just the Analyst which slipped a space. In my perspective, the editor should just strip away the prefix/trailing space: * -While Importing a DMN model from file Upload- (See [DROOLS-5062|https://issues.redhat.com/browse/DROOLS-5062]) * While editing a DRGElement and hitting OK to save its name For your consideration, thanks. > [DMN Designer] Editor allows node with prefix/trailing space > ------------------------------------------------------------ > > Key: DROOLS-5060 > URL: https://issues.redhat.com/browse/DROOLS-5060 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: ItemDefinition-white-space.png > > > I understand [DROOLS-5017] has been re-purposed to allow Info and Warn level messages be displayed on Stunner Validation dialog. That is fine. > But, imho, an UX point is not being considered, where is necessary instead. > By the DMN spec, a node should not have a prefix/trailing space, as space insensitivity would mandate 1 trailing or 2 trailing spaces are simply ignored etc. > The engine is lenient to avoid this crashing the evaluation, but still is a bad designed model to persist the node name (DRGElement name and its corresponding variable name) with those extra spaces IMHO. > Further, I consider is just the Analyst which slipped a space. > In my perspective, the editor should just strip away the prefix/trailing space: > * -While Importing a DMN model from file Upload- (See [DROOLS-5062|https://issues.redhat.com/browse/DROOLS-5062]) > * While editing a DRGElement and hitting OK to save its name > For your consideration, thanks. > h2. Manual acceptance test > - Rename a node, check undo/redo > - Rename node as ctrl-c/ctrl+v > - Try to use \tab in the middle of the name > - Leading space > - Trailing space > - Save and reopen > - Documentation tab > - Rename via node popup > - Rename via properties panel > - Rename via expression grid - where applicable -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5108) KieHelper.build is very slow on Drools 6.4.0.Final

by Ravi M (Jira)

Ravi M created DROOLS-5108: ------------------------------ Summary: KieHelper.build is very slow on Drools 6.4.0.Final Key: DROOLS-5108 URL: https://issues.redhat.com/browse/DROOLS-5108 Project: Drools Issue Type: Bug Components: core engine Reporter: Ravi M Assignee: Mario Fusco Tried build with 230 rules, it is taking nearly 10 seconds {code:java} org.kie.internal.utils.KieHelper kieHelper = new org.kie.internal.utils.KieHelper(); kieHelper.setClassLoader(this.getClass().getClassLoader()); kieHelper.addContent( drlContent, ResourceType.DRL ); Results res = kieHelper.verify(); if ( res.hasMessages( Message.Level.ERROR ) ) { throw new DroolsCompilationException("Exception while compiling rule "); } if ( kbConf == null ) { kbConf = KieServices.Factory.get().newKieBaseConfiguration(); } kbConf.setOption( EqualityBehaviorOption.EQUALITY ); KieBase kieBase = kieHelper.build( kbConf ); {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13152) WFLYEJB0094: EJB 3.1 FR 5.4.2 MessageDrivenBean does not implement 1 interface nor specifies message listener interface

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13152?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-13152: ----------------------------------- My proposal is to modify [MessageDrivenComponentDescriptionFactory|https://github.com/wildfly/wildf...] to search the super class {{ClassInfo}} in parent module, after failing to find it in the current module. As we've already got a non-null {{superClassDotName}}, so the super class must exist somewhere. Doing nothing after failing to find super class {{ClassInfo}} in current module is not right. I'll try it out and send the PR if it works. > WFLYEJB0094: EJB 3.1 FR 5.4.2 MessageDrivenBean does not implement 1 interface nor specifies message listener interface > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-13152 > URL: https://issues.redhat.com/browse/WFLY-13152 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.1.Final > Reporter: Rhuan Rocha > Assignee: Cheng Fang > Priority: Major > Attachments: lib.zip, samplemdbear.zip > > > The MDB does not works when it extends a superclass that comes from an external JAR and this super class implements the MessageListener. It generates this exception: > {code:java} > WFLYEJB0094: EJB 3.1 FR 5.4.2 MessageDrivenBean com.exemple.MyMDB does not implement 1 interface nor specifies message listener interface > {code} > These are what I have noted: > * It only happens in a EAR project. In a WAR project it works fine. > * It only happens when the abstract class come from an external JAR > * If the sub class implements directly the MessageListener or if the messageListenerInterface is defined in the annotation it works fine. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5107) A rule always fires with executable model for a constraint which has extra parentheses

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5107?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5107: -------------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) > A rule always fires with executable model for a constraint which has extra parentheses > -------------------------------------------------------------------------------------- > > Key: DROOLS-5107 > URL: https://issues.redhat.com/browse/DROOLS-5107 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.33.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > When you have a constraint with extra parentheses, > {noformat} > $p : Person((age > 30)) > {noformat} > executable-model generates a pattern without a constraint expr method so it always fires. > {code:java} > public static org.drools.model.Rule rule_R() { > final org.drools.model.Variable<org.drools.modelcompiler.domain.Person> var_$p = D.declarationOf(org.drools.modelcompiler.domain.Person.class, DomainClassesMetadataFBDA1ED637C8B60C741C0BDB502EB8F0.org_drools_modelcompiler_domain_Person_Metadata_INSTANCE, "$p"); > org.drools.model.Rule rule = D.rule("R").build(D.pattern(var_$p), > D.execute(() -> { > { > } > })); > return rule; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

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