June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3819) Rule Units 2.0: evaluate 7.x behavior and consider new design

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3819?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3819: ----------------------------------- Description: I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) *Deliverable*: PR and (if possible) design document was: I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) *Deliverable*: design document > Rule Units 2.0: evaluate 7.x behavior and consider new design > ------------------------------------------------------------- > > Key: DROOLS-3819 > URL: https://issues.jboss.org/browse/DROOLS-3819 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) > *Deliverable*: PR and (if possible) design document -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3819) Rule Units 2.0: evaluate 7.x behavior and consider new design

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3819?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3819: ----------------------------------- Issue Type: Task (was: Bug) Summary: Rule Units 2.0: evaluate 7.x behavior and consider new design (was: Rule Unit Handling: restore older behavior in new prototype) > Rule Units 2.0: evaluate 7.x behavior and consider new design > ------------------------------------------------------------- > > Key: DROOLS-3819 > URL: https://issues.jboss.org/browse/DROOLS-3819 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3819) Rule Units 2.0: evaluate 7.x behavior and consider new design

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3819?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3819: ----------------------------------- Description: I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) *Deliverable*: design document was:I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) > Rule Units 2.0: evaluate 7.x behavior and consider new design > ------------------------------------------------------------- > > Key: DROOLS-3819 > URL: https://issues.jboss.org/browse/DROOLS-3819 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) > *Deliverable*: design document -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4093) [DMN Designer] Sometimes shortcuts does not work when editing DataType items

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4093?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-4093: ---------------------------------------- Welcome back [~jomarko] :-) Yes please could you report it as a new JIRA.. IDK whether it's a regression or pre-existed? > [DMN Designer] Sometimes shortcuts does not work when editing DataType items > ---------------------------------------------------------------------------- > > Key: DROOLS-4093 > URL: https://issues.jboss.org/browse/DROOLS-4093 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Fix For: 7.23.0.Final > > > Sometimes when user are adding and/or editing Data Types, the keyboard shortcuts (like CTRL +S) stop working. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12155) Add X-XSS-Protection header to default management config

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFLY-12155?page=com.atlassian.jira.plugin... ] Jan Stourac updated WFLY-12155: ------------------------------- Description: Even though we should probably avoid using non-standardized HTTP headers, since there is already X-FRAME-OPTIONS present in a management WFCORE-1463, I propose to consider to add also [X-XSS-Protection|https://developer.mozilla.org/en-US/docs/Web/HTTP/Header...] header in a default configuration of the management too. Benefit is slightly improved security for customers using Web Console management. Viable value variants are one of the following two: {code} X-XSS-Protection: 1 X-XSS-Protection: 1; mode=block {code} Current header provided: {code} curl -v http://localhost:9990/console/index.html ... < HTTP/1.1 200 OK < Connection: keep-alive < Last-Modified: Wed, 29 May 2019 11:09:49 GMT < X-Frame-Options: SAMEORIGIN < Content-Length: 1289 < Content-Type: text/html < Accept-Ranges: bytes < Date: Mon, 03 Jun 2019 08:05:05 GMT ... {code} was: Even though we should probably avoid using non-standardized HTTP headers, since there is already X-FRAME-OPTIONS present in a management WFCORE-1463, I propose to consider to add also [X-XSS-PROTECTION|https://developer.mozilla.org/en-US/docs/Web/HTTP/Header...] header in a default configuration of the management too. Benefit is slightly improved security for customers using Web Console management. Viable value variants are one of the following two: {code} X-XSS-Protection: 1 X-XSS-Protection: 1; mode=block {code} > Add X-XSS-Protection header to default management config > -------------------------------------------------------- > > Key: WFLY-12155 > URL: https://issues.jboss.org/browse/WFLY-12155 > Project: WildFly > Issue Type: Enhancement > Components: Management > Affects Versions: 16.0.0.Final > Reporter: Jan Stourac > Assignee: Jeff Mesnil > Priority: Major > > Even though we should probably avoid using non-standardized HTTP headers, since there is already X-FRAME-OPTIONS present in a management WFCORE-1463, I propose to consider to add also [X-XSS-Protection|https://developer.mozilla.org/en-US/docs/Web/HTTP/Header...] header in a default configuration of the management too. > Benefit is slightly improved security for customers using Web Console management. > Viable value variants are one of the following two: > {code} > X-XSS-Protection: 1 > X-XSS-Protection: 1; mode=block > {code} > Current header provided: > {code} > curl -v http://localhost:9990/console/index.html > ... > < HTTP/1.1 200 OK > < Connection: keep-alive > < Last-Modified: Wed, 29 May 2019 11:09:49 GMT > < X-Frame-Options: SAMEORIGIN > < Content-Length: 1289 > < Content-Type: text/html > < Accept-Ranges: bytes > < Date: Mon, 03 Jun 2019 08:05:05 GMT > ... > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12156) Add X-Content-Type-Options header to default management config

by Jan Stourac (Jira)

Jan Stourac created WFLY-12156: ---------------------------------- Summary: Add X-Content-Type-Options header to default management config Key: WFLY-12156 URL: https://issues.jboss.org/browse/WFLY-12156 Project: WildFly Issue Type: Enhancement Components: Management Affects Versions: 16.0.0.Final Reporter: Jan Stourac Assignee: Jeff Mesnil Even though we should probably avoid using non-standardized HTTP headers, since there is already X-FRAME-OPTIONS present in a management WFCORE-1463, I propose to consider to add also [X-Content-Type-Options|https://developer.mozilla.org/en-US/docs/Web/HTTP/...] header in a default configuration of the management too. Benefit is slightly improved security for customers using Web Console management. Current header provided: {code} curl -v http://localhost:9990/console/index.html ... < HTTP/1.1 200 OK < Connection: keep-alive < Last-Modified: Wed, 29 May 2019 11:09:49 GMT < X-Frame-Options: SAMEORIGIN < Content-Length: 1289 < Content-Type: text/html < Accept-Ranges: bytes < Date: Mon, 03 Jun 2019 08:05:05 GMT ... {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12155) Add X-XSS-Protection header to default management config

by Jan Stourac (Jira)

Jan Stourac created WFLY-12155: ---------------------------------- Summary: Add X-XSS-Protection header to default management config Key: WFLY-12155 URL: https://issues.jboss.org/browse/WFLY-12155 Project: WildFly Issue Type: Enhancement Components: Management Affects Versions: 16.0.0.Final Reporter: Jan Stourac Assignee: Jeff Mesnil Even though we should probably avoid using non-standardized HTTP headers, since there is already X-FRAME-OPTIONS present in a management WFCORE-1463, I propose to consider to add also [X-XSS-PROTECTION|https://developer.mozilla.org/en-US/docs/Web/HTTP/Header...] header in a default configuration of the management too. Benefit is slightly improved security for customers using Web Console management. Viable value variants are one of the following two: {code} X-XSS-Protection: 1 X-XSS-Protection: 1; mode=block {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4093) [DMN Designer] Sometimes shortcuts does not work when editing DataType items

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4093?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-4093: ------------------------------------- [~dadossan] [~manstis] Hi, I had checked the shortcuts briefly as there was an update on Friday, I found the stop to work after constraint dialog is opened & closed. Should I report this? > [DMN Designer] Sometimes shortcuts does not work when editing DataType items > ---------------------------------------------------------------------------- > > Key: DROOLS-4093 > URL: https://issues.jboss.org/browse/DROOLS-4093 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Fix For: 7.23.0.Final > > > Sometimes when user are adding and/or editing Data Types, the keyboard shortcuts (like CTRL +S) stop working. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3907) [DMN Designer] (DEV) Add visual indicators for imported Nodes

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3907?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-3907: ------------------------------------------- Fix Version/s: 7.24.0.Final (was: 7.23.0.Final) > [DMN Designer] (DEV) Add visual indicators for imported Nodes > ------------------------------------------------------------- > > Key: DROOLS-3907 > URL: https://issues.jboss.org/browse/DROOLS-3907 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, UXTeam, drools-tools > Fix For: 7.24.0.Final > > Attachments: Screen Shot 2019-04-17 at 11.55.39 AM.png, read-only-gridC2.png, read-only-gridC2.png > > > Imported models are read-only. We need to show some form of visual indicator for both Nodes (Graph View) and Boxed Expressions (Grid View). Please see the attachments for proposals for the Grid View. > Design Resolution: > * Option C: https://issues.jboss.org/secure/attachment/12449764/read-only-gridC2.png > * Keeping the hover highlight per row cell as is, because when those elements are clicked the Property panel is updated/reflects. > * Use lock icon for canvas nodes: In the components list and in the graph nodes, as illustrated in: https://issues.jboss.org/secure/attachment/12449758/Screen%20Shot%202019-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3160) adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm)

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3160?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-3160: ------------------------------------------- Fix Version/s: 7.24.0.Final (was: 7.23.0.Final) > adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm) > ------------------------------------------------------------ > > Key: DROOLS-3160 > URL: https://issues.jboss.org/browse/DROOLS-3160 > Project: Drools > Issue Type: Feature Request > Reporter: Michael Biarnes Kiefer > Assignee: Toni Rikkola > Priority: Major > Fix For: 7.24.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2019