January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3514) [DMN Designer] Feel autocomplete, sintax highlighting and type checking.

by Thomas Mantegazzi (Jira)

Thomas Mantegazzi created DROOLS-3514: ----------------------------------------- Summary: [DMN Designer] Feel autocomplete, sintax highlighting and type checking. Key: DROOLS-3514 URL: https://issues.jboss.org/browse/DROOLS-3514 Project: Drools Issue Type: Feature Request Components: DMN Editor Affects Versions: 7.15.0.Final Reporter: Thomas Mantegazzi Assignee: Michael Anstis Attachments: image-2019-01-14-09-16-09-474.png, image-2019-01-14-09-16-30-813.png, image-2019-01-14-09-17-20-451.png When trying to write decisions, it would be nice to have some sintax highlighting, and autocomplete based on the inputs provided to the decision in the DRG. DRG: !image-2019-01-14-09-16-09-474.png|thumbnail! Data type: !image-2019-01-14-09-16-30-813.png|thumbnail! Feel expression: !image-2019-01-14-09-17-20-451.png|thumbnail! In this case, it would be nice that when we write "p" we get the suggestion "person". It would also be nice to get type checking, so that if we declare a DMN decision to have output of type : "number" we can not write a literal expression that outputs a String. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3513) [DMN Designer] Literal expression boxes can not be changed in haing

by Thomas Mantegazzi (Jira)

Thomas Mantegazzi created DROOLS-3513: ----------------------------------------- Summary: [DMN Designer] Literal expression boxes can not be changed in haing Key: DROOLS-3513 URL: https://issues.jboss.org/browse/DROOLS-3513 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.15.0.Final Reporter: Thomas Mantegazzi Assignee: Michael Anstis Attachments: image-2019-01-14-09-12-40-849.png If a more complex logic is inputed in a literal expression, it might be thate the literal expression becomes more than a few lines. At the moment it is not possible to resize the heignt of the literal expression box. !image-2019-01-14-09-12-40-849.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3512) [DMN Designer] Increase maximal size of diagram nodes, and include text wrapping.

by Thomas Mantegazzi (Jira)

Thomas Mantegazzi created DROOLS-3512: ----------------------------------------- Summary: [DMN Designer] Increase maximal size of diagram nodes, and include text wrapping. Key: DROOLS-3512 URL: https://issues.jboss.org/browse/DROOLS-3512 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.15.0.Final Reporter: Thomas Mantegazzi Assignee: Michael Anstis Attachments: image-2019-01-14-09-07-56-069.png If a decision name becomes too long the name will overflow the Decision diagram. !image-2019-01-14-09-07-56-069.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11558) Content-Type header is not set in HTTP response for directory resource in servlet directory-listing feature

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11558?page=com.atlassian.jira.plugin... ] Bartosz Baranowski reassigned WFLY-11558: ----------------------------------------- Assignee: Stuart Douglas (was: Bartosz Baranowski) > Content-Type header is not set in HTTP response for directory resource in servlet directory-listing feature > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-11558 > URL: https://issues.jboss.org/browse/WFLY-11558 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 15.0.0.Final > Reporter: Jan Stourac > Assignee: Stuart Douglas > Priority: Major > Attachments: helloworld-html5.war > > > [DefaultServlet|https://github.com/undertow-io/undertow/blob/master/servle...] does not set Content-Type HTTP header in response for the directory resource when directory-listing feature is enabled. > As browsers apparently try to guess appropriate Content-Type of the downloaded resource, this problem is not spotted unless in combination with [X-Content-Type-Options|https://developer.mozilla.org/en-US/docs/Web/HTTP/...] header is present in the HTTP response too. This header effectively discourages browser to guess the Content-Type of the resource. > Output for directory-listing request in attached reproducer [^helloworld-html5.war]: > {code} > $ curl -v http://127.0.0.1:8080/helloworld-html5/css/ >/dev/null > * Trying 127.0.0.1... > * TCP_NODELAY set > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0) > > GET /helloworld-html5/css/ HTTP/1.1 > > Host: 127.0.0.1:8080 > > User-Agent: curl/7.59.0 > > Accept: */* > > > < HTTP/1.1 200 OK > < Connection: keep-alive > < Content-Length: 824 > < Date: Fri, 04 Jan 2019 14:32:46 GMT > < > { [824 bytes data] > 100 824 100 824 0 0 804k 0 --:--:-- --:--:-- --:--:-- 804k > * Connection #0 to host 127.0.0.1 left intact > {code} > Notice that there is no Content-Type header in HTTP response. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3486) Scenario Simulation: Export agenda info from session to a report

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3486?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-3486: --------------------------------- Labels: (was: UX UXTeam) > Scenario Simulation: Export agenda info from session to a report > ---------------------------------------------------------------- > > Key: DROOLS-3486 > URL: https://issues.jboss.org/browse/DROOLS-3486 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > > Report information should at least contain information about test coverage and what rules fired and what not. Proposed format is CSV file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3486) Scenario Simulation: Export agenda info from session to a report

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3486?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-3486: -------------------------------------- [~aglass] I think for this ticket it is safe to remove the UX tags. There are plans for extracted report that you can download from the workbench. The report will have some layout done with HTML or PDF, but this ticket is just for raw file format with no UI. > Scenario Simulation: Export agenda info from session to a report > ---------------------------------------------------------------- > > Key: DROOLS-3486 > URL: https://issues.jboss.org/browse/DROOLS-3486 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: UX, UXTeam > > Report information should at least contain information about test coverage and what rules fired and what not. Proposed format is CSV file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11558) Content-Type header is not set in HTTP response for directory resource in servlet directory-listing feature

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11558?page=com.atlassian.jira.plugin... ] Bartosz Baranowski reassigned WFLY-11558: ----------------------------------------- Assignee: Bartosz Baranowski (was: Stuart Douglas) > Content-Type header is not set in HTTP response for directory resource in servlet directory-listing feature > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-11558 > URL: https://issues.jboss.org/browse/WFLY-11558 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 15.0.0.Final > Reporter: Jan Stourac > Assignee: Bartosz Baranowski > Priority: Major > Attachments: helloworld-html5.war > > > [DefaultServlet|https://github.com/undertow-io/undertow/blob/master/servle...] does not set Content-Type HTTP header in response for the directory resource when directory-listing feature is enabled. > As browsers apparently try to guess appropriate Content-Type of the downloaded resource, this problem is not spotted unless in combination with [X-Content-Type-Options|https://developer.mozilla.org/en-US/docs/Web/HTTP/...] header is present in the HTTP response too. This header effectively discourages browser to guess the Content-Type of the resource. > Output for directory-listing request in attached reproducer [^helloworld-html5.war]: > {code} > $ curl -v http://127.0.0.1:8080/helloworld-html5/css/ >/dev/null > * Trying 127.0.0.1... > * TCP_NODELAY set > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0) > > GET /helloworld-html5/css/ HTTP/1.1 > > Host: 127.0.0.1:8080 > > User-Agent: curl/7.59.0 > > Accept: */* > > > < HTTP/1.1 200 OK > < Connection: keep-alive > < Content-Length: 824 > < Date: Fri, 04 Jan 2019 14:32:46 GMT > < > { [824 bytes data] > 100 824 100 824 0 0 804k 0 --:--:-- --:--:-- --:--:-- 804k > * Connection #0 to host 127.0.0.1 left intact > {code} > Notice that there is no Content-Type header in HTTP response. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11565) WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11565?page=com.atlassian.jira.plugin... ] Bartosz Baranowski commented on WFLY-11565: ------------------------------------------- [~dsahu030686] Could you please attach reproducer? > WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204 > ------------------------------------------------------------------------------------------- > > Key: WFLY-11565 > URL: https://issues.jboss.org/browse/WFLY-11565 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final > Reporter: Deepak Sahu > Assignee: Bartosz Baranowski > Priority: Major > > I am using WildFly Server 9.0.0 Final, Javax ws, Jersey for developing Rest APIs. For all the responses whose httpStatus code is 204, the wildfly server adds Transfer encoding Chunked in the response header, which is not correct as per the Rest Standards. Because of this behavior some of the RestAPI clients hang, as they keep waiting for the response (which is not at all there). > To verify the issue, I tried the same with Springboot instead of deploying the war in WildFly and the Response Header was not added with Transfer Encoding Chuncked. > Let me know if some other information is required to fix this issue, if this is already fixed is there any patch for this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11565) WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11565?page=com.atlassian.jira.plugin... ] Bartosz Baranowski reassigned WFLY-11565: ----------------------------------------- Assignee: Bartosz Baranowski (was: Jason Greene) > WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204 > ------------------------------------------------------------------------------------------- > > Key: WFLY-11565 > URL: https://issues.jboss.org/browse/WFLY-11565 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final > Reporter: Deepak Sahu > Assignee: Bartosz Baranowski > Priority: Major > > I am using WildFly Server 9.0.0 Final, Javax ws, Jersey for developing Rest APIs. For all the responses whose httpStatus code is 204, the wildfly server adds Transfer encoding Chunked in the response header, which is not correct as per the Rest Standards. Because of this behavior some of the RestAPI clients hang, as they keep waiting for the response (which is not at all there). > To verify the issue, I tried the same with Springboot instead of deploying the war in WildFly and the Response Header was not added with Transfer Encoding Chuncked. > Let me know if some other information is required to fix this issue, if this is already fixed is there any patch for this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting

by tao zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ] tao zhu commented on DROOLS-3492: --------------------------------- Thanks [~aglass] I am working on it. > Create UX proposal to show/edit Test Scenario (Preview) global setting > ---------------------------------------------------------------------- > > Key: DROOLS-3492 > URL: https://issues.jboss.org/browse/DROOLS-3492 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXD, UXTeam > Attachments: 11unnamed.png, TestScenario_Cheatsheet.png, TestScenario_TestEditor.png, TestScenario_TestReport.png, TestScenario_whole.png > > > As user I want to be able to see/edit editor global settings. > For instance DMN file linked to the scenario or the Session name of a Rule scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

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