June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5384) Clicking rightmost column's header in DMN decision table raises an error

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5384?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-5384: ------------------------------------------- Oh, I found an interesting condition to reproduce the issue. Please look at the left side of the attached dmn-decision-table-error-popup-7.38.0.png. You will notice that decision table is not fully displayed (The column "Violation.Type" is half-hidden). In this case, I can reproduce the issue (Note: At the first time, it raises an error popup. After that, the header is unresponsive). So you may need to zoom your browser to reproduce the issue. > Clicking rightmost column's header in DMN decision table raises an error > ------------------------------------------------------------------------ > > Key: DROOLS-5384 > URL: https://issues.redhat.com/browse/DROOLS-5384 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: dmn-decision-table-error-popup-7.38.0.png, drools5384.mp4 > > > When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. (At the first time, it raises an error popup. After that, the header is unresponsive) > See screenshot. > Chrome 80.0.3987.122 > Firefox 60.6.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5384) Clicking rightmost column's header in DMN decision table raises an error

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5384?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5384: -------------------------------------- Description: When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. (At the first time, it raises an error popup. After that, the header is unresponsive) See screenshot. Chrome 80.0.3987.122 Firefox 60.6.2 was: When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. (he first time, it raises an error popup. After that, the header is unresponsive) See screenshot. Chrome 80.0.3987.122 Firefox 60.6.2 > Clicking rightmost column's header in DMN decision table raises an error > ------------------------------------------------------------------------ > > Key: DROOLS-5384 > URL: https://issues.redhat.com/browse/DROOLS-5384 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: dmn-decision-table-error-popup-7.38.0.png, drools5384.mp4 > > > When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. (At the first time, it raises an error popup. After that, the header is unresponsive) > See screenshot. > Chrome 80.0.3987.122 > Firefox 60.6.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5384) Clicking rightmost column's header in DMN decision table raises an error

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5384?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5384: -------------------------------------- Description: When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. (he first time, it raises an error popup. After that, the header is unresponsive) See screenshot. Chrome 80.0.3987.122 Firefox 60.6.2 was: When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. See screenshot. Chrome 80.0.3987.122 Firefox 60.6.2 > Clicking rightmost column's header in DMN decision table raises an error > ------------------------------------------------------------------------ > > Key: DROOLS-5384 > URL: https://issues.redhat.com/browse/DROOLS-5384 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: dmn-decision-table-error-popup-7.38.0.png, drools5384.mp4 > > > When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. (he first time, it raises an error popup. After that, the header is unresponsive) > See screenshot. > Chrome 80.0.3987.122 > Firefox 60.6.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5384) Clicking rightmost column's header in DMN decision table raises an error

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5384?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-5384: ------------------------------------------- Hmm, I tested with a current master build (business-central-7.39.0-SNAPSHOT-wildfly18.war) but still see the same error popup. > Clicking rightmost column's header in DMN decision table raises an error > ------------------------------------------------------------------------ > > Key: DROOLS-5384 > URL: https://issues.redhat.com/browse/DROOLS-5384 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: dmn-decision-table-error-popup-7.38.0.png, drools5384.mp4 > > > When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. > See screenshot. > Chrome 80.0.3987.122 > Firefox 60.6.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13358) Tests for WFCORE-4950 - Regression: Legacy Ldap Realm securing EJB with JDK8 not working

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13358?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13358: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Tests for WFCORE-4950 - Regression: Legacy Ldap Realm securing EJB with JDK8 not working > ---------------------------------------------------------------------------------------- > > Key: WFLY-13358 > URL: https://issues.redhat.com/browse/WFLY-13358 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Reporter: Darran Lofthouse > Assignee: Ricardo Martin Camarero > Priority: Critical > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > This is likely to actually be a WFCORE issue but as this is fixed a test case to reproduce should be added to the testsuite if appropriate. > So far this seems a fairly generic issue an since WildFly 17 we must have run the testsuite against Java 8 100s if not 1000s of times so it is not appropriate to be reliant on an internal testsuite to detect the issue nine months or more later. > The following issue describes the issue in relation to EAP: - > https://issues.redhat.com/browse/JBEAP-19195 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13412) Add Json Merge Patch support

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13412?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13412: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Add Json Merge Patch support > ---------------------------- > > Key: WFLY-13412 > URL: https://issues.redhat.com/browse/WFLY-13412 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 19.0.0.Final > Reporter: Jim Ma > Assignee: Jim Ma > Priority: Major > Fix For: 21.0.0.Beta1 > > > This feature request for add json merge patch support and provide configuration to disable Resteasy PatchMethodFilter and allow user to configure customized PathMethodFilter to handle json patch request. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13220) A DeploymentException must be thrown if configured to use a PrivateKey

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13220?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13220: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > A DeploymentException must be thrown if configured to use a PrivateKey > ---------------------------------------------------------------------- > > Key: WFLY-13220 > URL: https://issues.redhat.com/browse/WFLY-13220 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Affects Versions: 19.0.0.Beta3 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Beta1 > > > From section 9.2.0 of the Eclipse MicroProfile JWT specification, implementations are required to throw a DeploymentException when given a PrivateKey in any format. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13065) Options for reverse-proxy max-request-time and connection-idle-timeout are specified as seconds

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13065?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13065: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Options for reverse-proxy max-request-time and connection-idle-timeout are specified as seconds > ----------------------------------------------------------------------------------------------- > > Key: WFLY-13065 > URL: https://issues.redhat.com/browse/WFLY-13065 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 19.0.0.Beta1 > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Minor > Fix For: 21.0.0.Beta1 > > > In the reverse-proxy configuration the options {{max-request-time}} and {{connection-idle-timeout}} are specified and managed as seconds in CLI, when they are really milliseconds in undertow. > {noformat} > /subsystem=undertow/configuration=handler/reverse-proxy=LBProxy:read-resource-description > ... > "connection-idle-timeout" => { > "type" => INT, > "description" => "The amount of time a connection can be idle before it will be closed. Connections will not time out > once the pool size is down to the configured minimum (as configured by cached-connections-per-thread)", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => 60L, > "unit" => "SECONDS", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > }, > ... > "max-request-time" => { > "type" => INT, > "description" => "The maximum time that a proxy request can be active for, before being killed", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => -1, > "unit" => "SECONDS", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > }, > ... > {noformat} > The class [ReverseProxyHandler|https://github.com/wildfly/wildfly/blob/master/undert...] just passes the value (no modification) to undertow and it's clearly millis in undertow, for example the [max-request-time|https://github.com/undertow-io/undertow/blob/master/core...]. > I has suffered this confusion myself doing some tests, I set 60 as the max request time, and it was too short in my env (because they are millis instead of seconds). > We need to change description to millis to respect current configurations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12866) Add MP Metrics test for Webservice

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12866?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12866: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Add MP Metrics test for Webservice > ----------------------------------- > > Key: WFLY-12866 > URL: https://issues.redhat.com/browse/WFLY-12866 > Project: WildFly > Issue Type: Task > Components: Web Services > Affects Versions: 18.0.1.Final > Reporter: Jim Ma > Assignee: Jim Ma > Priority: Minor > Fix For: 21.0.0.Beta1 > > > Add a Microprofile-metrics test to demonstrate this works for webservice endpoint -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13434) Update EJB / Elytron Integration to use SecurityMetaData in DeploymentUnit

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13434?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13434: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Update EJB / Elytron Integration to use SecurityMetaData in DeploymentUnit > -------------------------------------------------------------------------- > > Key: WFLY-13434 > URL: https://issues.redhat.com/browse/WFLY-13434 > Project: WildFly > Issue Type: Task > Components: EJB, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Beta1 > > > WFCORE-4962 is adding a new SecurityMetaData class and adding as an attachment to the DeploymentUnit. > If this contains a ServiceName for a security domain this should be used instead of any local mapping in the subsystem, additionally the presence of this domain should act as a flag to enable the Elytron form of interceptors. > Also if an Elytron SecurityDomain is selected for the deployment it's ServiceName should be set on the SecurityMetaData instance. -- 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