[JBoss JIRA] (DROOLS-3175) [DMN Designer] keyboard context menu invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3175?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3175:
--------------------------------
Description:
User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
h2. TODO
- DMN - undefined cell
- DMN - After selection of menu item the focus is lost
- Scenario - proper menu for description column
- Scenario - enable menu even when not bound
- Tests
was:
User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
h2. TODO
- DMN - undefined cell
- DMN - After selection of menu item the focus is lost
- Scenario - proper menu for description column
- Scenario - enable menu even when not bound
> [DMN Designer] keyboard context menu invocation
> -----------------------------------------------
>
> Key: DROOLS-3175
> URL: https://issues.jboss.org/browse/DROOLS-3175
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
> h2. TODO
> - DMN - undefined cell
> - DMN - After selection of menu item the focus is lost
> - Scenario - proper menu for description column
> - Scenario - enable menu even when not bound
> - Tests
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11031) Json encoding of Access Log Events
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11031?page=com.atlassian.jira.plugin... ]
James Perkins reassigned WFLY-11031:
------------------------------------
Assignee: James Perkins (was: Stuart Douglas)
> Json encoding of Access Log Events
> ----------------------------------
>
> Key: WFLY-11031
> URL: https://issues.jboss.org/browse/WFLY-11031
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Frank Schmager
> Assignee: James Perkins
> Priority: Minor
>
> h1. Request
> It should be possible to emit access log events json encoded to allow log aggregation systems to ingest pre-parsed events for filtering and analytics.
> h1. Background
> Application logs can be emitted [json encoded|https://wildscribe.github.io/WildFly/13.0/subsystem/logging/json-formatter/index.html] allowing log aggregation systems like logstash/ELK to ingest and parse the events. This is especially important when working with containers, but anything requiring log aggregation would benefit. Not all log aggregation systems allow after-the-fact parsing of log events (e.g. Kibana) and developers don't have access to the log aggregator to install a parser like logstash/filebeat.
> [Access log events|https://wildscribe.github.io/WildFly/13.0/subsystem/undertow/server/host/setting/access-log/index.html], however, can't be json encoded. The whole log event can be, but what's important about access log events can't.
> h2. Example result
> There are many ways to encode the event into json. Ideally it would be configurable. One way would be to use {{message}}, but instead of it just containing a {{String}} it could contain json. However, abusing the {{message}} field might not work because it is of type {{String|text}}. So even if it contained valid json, it wouldn't be processed as such. Separate fields might need to be used. Using {{message}} is probably preferred because if not, what else would that field contain?
> {code:json}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": {
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> ...
> }
> ...
> # alternatively
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> "remoteUser": "200",
> "dateTime": "[14/Sep/2018:20:59:37 +0000]",
> "requestLine": "GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0",
> "status": "200",
> "bytesSent": "81862",
> "timeTaken": "10",
> "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36"
> ...
> {code}
> h2. Attempted Workaround
> Making the pattern look like json failed due to double quote escaping:
> {code:xml}
> <access-log pattern='{\"x-forwarded-for\":\"%{i,X-Forwarded-For}\",\"remoteHost\":\"%h\",\"remoteUser\":\"%s\",\"dateTime\":\"%t\",\"requestLine\":\"%r\",\"status\":\"%s\",\"bytesSent\":\"%b\",\"timeTaken\":\"%D\",\"userAgent\":\"%{i,User-Agent}\"}' use-server-log="true" />
> {code}
> h3. Result
> {code}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": "{\\\"x-forwarded-for\\\":\\\"-\\\",\\\"remoteHost\\\":\\\"172.20.2.1\\\",\\\"remoteUser\\\":\\\"200\\\",\\\"dateTime\\\":\\\"[14/Sep/2018:20:59:37 +0000]\\\",\\\"requestLine\\\":\\\"GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0\\\",\\\"status\\\":\\\"200\\\",\\\"bytesSent\\\":\\\"81862\\\",\\\"timeTaken\\\":\\\"10\\\",\\\"userAgent\\\":\\\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36\\\"}",
> {code}
> h2. Json formatting log configuration
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:logging:5.0">
> <console-handler name="CONSOLE">
> <level name="DEBUG"/>
> <formatter>
> <named-formatter name="JSON_FORMATTER"/>
> </formatter>
> </console-handler>
> ...
> <formatter name="JSON_FORMATTER">
> <json-formatter>
> <exception-output-type value="formatted"/>
> <key-overrides timestamp="@timestamp" loggerName="logger_name"/>
> <meta-data>
> <property name="@version" value="1"/>
> </meta-data>
> </json-formatter>
> </formatter>
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11654) Json encoding of Access Log Events
by James Perkins (Jira)
James Perkins created WFLY-11654:
------------------------------------
Summary: Json encoding of Access Log Events
Key: WFLY-11654
URL: https://issues.jboss.org/browse/WFLY-11654
Project: WildFly
Issue Type: Feature Request
Components: Web (Undertow)
Reporter: Frank Schmager
Assignee: Stuart Douglas
h1. Request
It should be possible to emit access log events json encoded to allow log aggregation systems to ingest pre-parsed events for filtering and analytics.
h1. Background
Application logs can be emitted [json encoded|https://wildscribe.github.io/WildFly/13.0/subsystem/logging/json-formatter/index.html] allowing log aggregation systems like logstash/ELK to ingest and parse the events. This is especially important when working with containers, but anything requiring log aggregation would benefit. Not all log aggregation systems allow after-the-fact parsing of log events (e.g. Kibana) and developers don't have access to the log aggregator to install a parser like logstash/filebeat.
[Access log events|https://wildscribe.github.io/WildFly/13.0/subsystem/undertow/server/host/setting/access-log/index.html], however, can't be json encoded. The whole log event can be, but what's important about access log events can't.
h2. Example result
There are many ways to encode the event into json. Ideally it would be configurable. One way would be to use {{message}}, but instead of it just containing a {{String}} it could contain json. However, abusing the {{message}} field might not work because it is of type {{String|text}}. So even if it contained valid json, it wouldn't be processed as such. Separate fields might need to be used. Using {{message}} is probably preferred because if not, what else would that field contain?
{code:json}
...
"@timestamp": "2018-09-14T20:59:37.530Z",
...
"message": {
"x-forwarded-for": "-",
"remoteHost": "172.20.2.1",
...
}
...
# alternatively
"x-forwarded-for": "-",
"remoteHost": "172.20.2.1",
"remoteUser": "200",
"dateTime": "[14/Sep/2018:20:59:37 +0000]",
"requestLine": "GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0",
"status": "200",
"bytesSent": "81862",
"timeTaken": "10",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36"
...
{code}
h2. Attempted Workaround
Making the pattern look like json failed due to double quote escaping:
{code:xml}
<access-log pattern='{\"x-forwarded-for\":\"%{i,X-Forwarded-For}\",\"remoteHost\":\"%h\",\"remoteUser\":\"%s\",\"dateTime\":\"%t\",\"requestLine\":\"%r\",\"status\":\"%s\",\"bytesSent\":\"%b\",\"timeTaken\":\"%D\",\"userAgent\":\"%{i,User-Agent}\"}' use-server-log="true" />
{code}
h3. Result
{code}
...
"@timestamp": "2018-09-14T20:59:37.530Z",
...
"message": "{\\\"x-forwarded-for\\\":\\\"-\\\",\\\"remoteHost\\\":\\\"172.20.2.1\\\",\\\"remoteUser\\\":\\\"200\\\",\\\"dateTime\\\":\\\"[14/Sep/2018:20:59:37 +0000]\\\",\\\"requestLine\\\":\\\"GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0\\\",\\\"status\\\":\\\"200\\\",\\\"bytesSent\\\":\\\"81862\\\",\\\"timeTaken\\\":\\\"10\\\",\\\"userAgent\\\":\\\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36\\\"}",
{code}
h2. Json formatting log configuration
{code:xml}
<subsystem xmlns="urn:jboss:domain:logging:5.0">
<console-handler name="CONSOLE">
<level name="DEBUG"/>
<formatter>
<named-formatter name="JSON_FORMATTER"/>
</formatter>
</console-handler>
...
<formatter name="JSON_FORMATTER">
<json-formatter>
<exception-output-type value="formatted"/>
<key-overrides timestamp="@timestamp" loggerName="logger_name"/>
<meta-data>
<property name="@version" value="1"/>
</meta-data>
</json-formatter>
</formatter>
...
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-10937) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10937?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-10937:
--------------------------------------
Yes. In the attached {{standalone.conf.bat}} it appears to be above that label.
> Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
> -------------------------------------------------------------------------------
>
> Key: WFLY-10937
> URL: https://issues.jboss.org/browse/WFLY-10937
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Assignee: Richard Opalka
> Priority: Blocker
> Labels: Java11, blocker-WF14, jdk11
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
> Attachments: appclient.conf.bat
>
>
> Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
> *Affected scripts*
> * appclient
> * jdr
> * wsconsume
> * wsprovide
> *Example of logs*
> {noformat}
> [mkopecky@dhcp-10-40-4-197 bin]$ ./jdr.sh
> org.jboss.modules.ModuleNotFoundException: java.se
> at org.jboss.modules.Module.addPaths(Module.java:1266)
> at org.jboss.modules.Module.link(Module.java:1622)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> at org.jboss.modules.Main.main(Main.java:437)
> [mkopecky@dhcp-10-40-4-197 bin]$
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3554) KieContainer#updateToVersion removing rules with accumulate
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3554?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-3554:
--------------------------------
Sprint: 2019 Week 02-04, 2019 Week 05-07 (was: 2019 Week 02-04)
> KieContainer#updateToVersion removing rules with accumulate
> -----------------------------------------------------------
>
> Key: DROOLS-3554
> URL: https://issues.jboss.org/browse/DROOLS-3554
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.16.0.Final
> Reporter: Olga Rodionova
> Assignee: Mario Fusco
> Priority: Major
> Attachments: RuleRemovalTest.java, SimpleRuleWithAccumulate.drl
>
>
> Consider a rule with accumulate pattern in the LHS which logically inserts an object in the RHS. Build the KieModule from the KieFileSystem including this rule, create the KieContainer and the KieSession. Insert the facts. Everything works fine.
> Create a new KieModule excluding this rule from the KieFileSystem, update the KieContainer. Expect the logically inserted fact to be retracted, as the rule which trigged its creation is no longer present. Turns out that the fact is still present in the working memory
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3556) 'update' works differently than 'modify' when using dialect "mvel" with property reactive
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3556?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-3556:
--------------------------------
Sprint: 2019 Week 02-04, 2019 Week 05-07 (was: 2019 Week 02-04)
> 'update' works differently than 'modify' when using dialect "mvel" with property reactive
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-3556
> URL: https://issues.jboss.org/browse/DROOLS-3556
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.14.0.Final
> Environment: - Red Hat Decision Manager
> - 7.2.0
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: updatePropertyReactive.zip
>
>
> Behavior of 'update' is different from 'modify' when dialect "mvel" is used with property reactive.
> In case of reproducer, when using update() after fact modification, the rule is continuously executed even though the condition no longer match.(i.e. re-evaluation does not work as expected)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3175) [DMN Designer] keyboard context menu invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3175?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3175:
--------------------------------
Description:
User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
h2. TODO
- DMN - undefined cell
- DMN - After selection of menu item the focus is lost
- Scenario - proper menu for description column
- Scenario - enable menu even when not bound
was:
User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
h2. TODO
- DMN - undefined cell
- DMN After selection of menu item the focus is lost
> [DMN Designer] keyboard context menu invocation
> -----------------------------------------------
>
> Key: DROOLS-3175
> URL: https://issues.jboss.org/browse/DROOLS-3175
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
> h2. TODO
> - DMN - undefined cell
> - DMN - After selection of menu item the focus is lost
> - Scenario - proper menu for description column
> - Scenario - enable menu even when not bound
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3175) [DMN Designer] keyboard context menu invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3175?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3175:
--------------------------------
Description:
User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
h2. TODO
- DMN - undefined cell
- DMN After selection of menu item the focus is lost
was:User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
> [DMN Designer] keyboard context menu invocation
> -----------------------------------------------
>
> Key: DROOLS-3175
> URL: https://issues.jboss.org/browse/DROOLS-3175
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
> h2. TODO
> - DMN - undefined cell
> - DMN After selection of menu item the focus is lost
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3021:
---------------------------------------
Sprint: 2019 Week 02-04, 2019 Week 05-07 (was: 2019 Week 02-04)
> [DMN Designer] Data Types - Constraints - Enumeration component
> ---------------------------------------------------------------
>
> Key: DROOLS-3021
> URL: https://issues.jboss.org/browse/DROOLS-3021
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: future.png, prototype.png
>
>
> - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded;
> !prototype.png|thumbnail!
> - The component contains a dynamic list to insert the possible values
> - The input is a simple input without any validation
> This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}):
> !future.png|thumbnail!
> ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months