[JBoss JIRA] (DROOLS-4364) [DMN Designer] Documentation - Download buttons UX
by Margot Menestrot (Jira)
Margot Menestrot created DROOLS-4364:
----------------------------------------
Summary: [DMN Designer] Documentation - Download buttons UX
Key: DROOLS-4364
URL: https://issues.jboss.org/browse/DROOLS-4364
Project: Drools
Issue Type: Bug
Components: DMN Editor
Reporter: Margot Menestrot
Assignee: Margot Menestrot
Attachments: component-1.png, component-2.png, component-3.png
h3. Context:
Today users can:
1) Download the diagram picture by using this component:
!component-1.png|thumbnail!
2) Download the DMN file by using this component:
!component-2.png|thumbnail!
3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
!component-3.png|thumbnail!
4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
!component-3.png|thumbnail!
----
h3. Problem:
The "Download" concept is getting confusing for users.
As a user, I want to be able to:
- Download the documentation as a .PDF file
- Download the documentation as a .DOC file
- Print the documentation
----
h3. Notice:
This component can be removed (if UX considers that it's necessary):
!component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (DROOLS-4363) Improve the comprehensive Readme
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4363?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-4363:
----------------------------------
Description:
Improve the readme in the @TODO sections , with feedbacks and with a Drools sections
Add description about how to user DroolsExecutor to wrap side effects and guarantee that are executed only by the leader
was:Improve the readme in the @TODO sections , with feedbacks and with a Drools sections
> Improve the comprehensive Readme
> ---------------------------------
>
> Key: DROOLS-4363
> URL: https://issues.jboss.org/browse/DROOLS-4363
> Project: Drools
> Issue Type: Task
> Reporter: Massimiliano Dessi
> Assignee: Massimiliano Dessi
> Priority: Major
>
> Improve the readme in the @TODO sections , with feedbacks and with a Drools sections
> Add description about how to user DroolsExecutor to wrap side effects and guarantee that are executed only by the leader
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (DROOLS-4288) Infinite recursion in drools after version change from v7.20 to v7.21
by Geogie Tom (Jira)
[ https://issues.jboss.org/browse/DROOLS-4288?page=com.atlassian.jira.plugi... ]
Geogie Tom closed DROOLS-4288.
------------------------------
All the issues are fixed, except the static method scenario which is not a major concern. So concluding.
> Infinite recursion in drools after version change from v7.20 to v7.21
> ---------------------------------------------------------------------
>
> Key: DROOLS-4288
> URL: https://issues.jboss.org/browse/DROOLS-4288
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.21.0.Final, 7.22.0.Final, 7.23.0.Final
> Environment: Both Mac and Windows
> Reporter: Geogie Tom
> Assignee: Mario Fusco
> Priority: Major
> Fix For: 7.25.0.Final
>
> Attachments: Screen Shot 2019-07-10 at 3.53.10 PM.png, Screen Shot 2019-07-10 at 5.56.32 PM.png, Screen Shot 2019-07-10 at 5.59.28 PM.png, error.png, pojo.png, static.png, static_error.png
>
>
> When there is a version change in drools-compiler from `7.20.0.Final` to `7.21.0.Final` some rules are looping recursively.
> *Code in github:*
> [The working version|https://github.com/padippist/DroolsIssueReporting/tree/issue_v_7.20]
> [The recursively looping version|https://github.com/padippist/DroolsIssueReporting/tree/issue_v_7.21]
> [The change between working and looping version|https://github.com/padippist/DroolsIssueReporting/compare/issue_v...]
> *More details*
> When I fire a rule whose `then` part modifies a fact that is already checked in the `when` part:
> {code:java}
> rule "rule 1.1"
> when
> $sampleDomain: SampleDomain(instanceVariable2 == "Value of instance variable")
> then
> System.out.println("Rule 1.1 fired");
> modify($sampleDomain){
> setInstanceVariable1(3)
> }
> end
> {code}
> it doesn't loop recursively.
> But when I call another rule which call a static function from another class:
> {code:java}
> rule "rule 1.2"
> when
> $sampleDomain: SampleDomain(CoreUtils.anotherFunction())
> then
> System.out.println("Rule 1.2 fired");
> modify($sampleDomain){
> setInstanceVariable1(3)
> }
> end
> {code}
> it loops recursively.
> The class with static function is
> {code:java}
> import com.drool_issue.domain.SampleDomain;
> public class CoreUtils {
>
> public static boolean anotherFunction() {
> System.out.println("anotherFunction() inside CoreUtils");
> return true;
> }
>
> public static boolean anotherFunction(SampleDomain sampleDomain) {
> System.out.println("anotherFunction(SampleDomain sampleDomain) inside CoreUtils");
> return true;
> }
> }
> {code}
> My domain file is:
> {code:java}
> public class SampleDomain {
> private int instanceVariable1;
> private String instanceVariable2;
> private int instanceVariable3;
>
>
> public int getInstanceVariable1() {
> return instanceVariable1;
> }
> public void setInstanceVariable1(int instanceVariable1) {
> this.instanceVariable1 = instanceVariable1;
> }
> public String getInstanceVariable2() {
> return instanceVariable2;
> }
> public void setInstanceVariable2(String instanceVariable2) {
> this.instanceVariable2 = instanceVariable2;
> }
> public int getInstanceVariable3() {
> return instanceVariable3;
> }
> public void setInstanceVariable3(int instanceVariable3) {
> this.instanceVariable3 = instanceVariable3;
> }
>
>
> }
> {code}
> This is only caused after version change from `7.20.0.Final` to `7.21.0.Final`. Any guess on what the problem might be?
> When I further looked into the problem I saw this too.
> When we add two functions into the `SampleDomain` class ie
> {code:java}
> public boolean anotherFunction() {
> return true;
> }
>
> public boolean anotherFunction(SampleDomain sampleDomain) {
> return true;
> }
> {code}
> and use this in the rule like:
> {code:java}
> rule "rule 1.4"
> when
> $sampleDomain: SampleDomain(anotherFunction())
> then
> System.out.println("Rule 1.4 fired");
> modify($sampleDomain){
> setInstanceVariable1(3)
> }
> end
> {code}
> and
> {code:java}
> rule "rule 1.5"
> when
> $sampleDomain: SampleDomain(anotherFunction($sampleDomain))
> then
> System.out.println("Rule 1.5 fired");
> modify($sampleDomain){
> setInstanceVariable3(4)
> }
> end
> {code}
> these also loops recursively.
> *Code in github:*
> [The recursive looping when using non static methods|https://github.com/padippist/DroolsIssueReporting/tree/issue_v_7....]
> [The change between working and above version|https://github.com/padippist/DroolsIssueReporting/compare/issue_v...]
> Also when any of the static method is made non static then method from the domain class is called even though the static method is specified in the rule.
> *Code portions to be noted here are:*
> [Rule where static method is called.|https://github.com/padippist/DroolsIssueReporting/blob/bde2804b25...]
> [Another rule which also call the static method.|https://github.com/padippist/DroolsIssueReporting/blob/bde2804b25...]
> [The static access modifier removed from the functions which where previously static.|https://github.com/padippist/DroolsIssueReporting/compare/issue_v...]
> *Code in github:*
> [Weird behaviour when removing static modifier for the functions.|https://github.com/padippist/DroolsIssueReporting/tree/issue_v...]
> [The change between working and above version|https://github.com/padippist/DroolsIssueReporting/compare/issue_v...]
> *All this are caused in versions after `7.20.0.Final`, ie `7.21.0.Final`, `7.22.0.Final` and `7.23.0.Final`*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (WFCORE-4532) Investigate new JDK 13 regressions
by Richard Opalka (Jira)
[ https://issues.jboss.org/browse/WFCORE-4532?page=com.atlassian.jira.plugi... ]
Richard Opalka commented on WFCORE-4532:
----------------------------------------
Thanks for info [~jaikiran]
> Investigate new JDK 13 regressions
> ----------------------------------
>
> Key: WFCORE-4532
> URL: https://issues.jboss.org/browse/WFCORE-4532
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: Richard Opalka
> Priority: Critical
> Labels: jdk13
>
> Latest Open JDK 13 Early Access 25 introduced six new regressions in our test suites.
> Failing tests in WILDFLY-CORE are:
> * wildfly-core/elytron/src/test/java/org/wildfly/extension/elytron/TlsTestCase.java
> * wildfly-core/testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosHttpMgmtSaslTestCase.java
> * wildfly-core/testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosNativeMgmtSaslTestCase.java
> Failing tests in WILDFLY are:
> * wildfly/testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/CertificateRolesLoginModuleTestCase.java
> * wildfly/testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/DatabaseCertLoginModuleTestCase.java
> * wildfly/testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/HTTPSWebConnectorTestCase.java
> Could somebody from our security team have a look what is going on [~darran] ?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (DROOLS-4288) Infinite recursion in drools after version change from v7.20 to v7.21
by Geogie Tom (Jira)
[ https://issues.jboss.org/browse/DROOLS-4288?page=com.atlassian.jira.plugi... ]
Geogie Tom commented on DROOLS-4288:
------------------------------------
[~mfusco] Thanks man.
> Infinite recursion in drools after version change from v7.20 to v7.21
> ---------------------------------------------------------------------
>
> Key: DROOLS-4288
> URL: https://issues.jboss.org/browse/DROOLS-4288
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.21.0.Final, 7.22.0.Final, 7.23.0.Final
> Environment: Both Mac and Windows
> Reporter: Geogie Tom
> Assignee: Mario Fusco
> Priority: Major
> Fix For: 7.25.0.Final
>
> Attachments: Screen Shot 2019-07-10 at 3.53.10 PM.png, Screen Shot 2019-07-10 at 5.56.32 PM.png, Screen Shot 2019-07-10 at 5.59.28 PM.png, error.png, pojo.png, static.png, static_error.png
>
>
> When there is a version change in drools-compiler from `7.20.0.Final` to `7.21.0.Final` some rules are looping recursively.
> *Code in github:*
> [The working version|https://github.com/padippist/DroolsIssueReporting/tree/issue_v_7.20]
> [The recursively looping version|https://github.com/padippist/DroolsIssueReporting/tree/issue_v_7.21]
> [The change between working and looping version|https://github.com/padippist/DroolsIssueReporting/compare/issue_v...]
> *More details*
> When I fire a rule whose `then` part modifies a fact that is already checked in the `when` part:
> {code:java}
> rule "rule 1.1"
> when
> $sampleDomain: SampleDomain(instanceVariable2 == "Value of instance variable")
> then
> System.out.println("Rule 1.1 fired");
> modify($sampleDomain){
> setInstanceVariable1(3)
> }
> end
> {code}
> it doesn't loop recursively.
> But when I call another rule which call a static function from another class:
> {code:java}
> rule "rule 1.2"
> when
> $sampleDomain: SampleDomain(CoreUtils.anotherFunction())
> then
> System.out.println("Rule 1.2 fired");
> modify($sampleDomain){
> setInstanceVariable1(3)
> }
> end
> {code}
> it loops recursively.
> The class with static function is
> {code:java}
> import com.drool_issue.domain.SampleDomain;
> public class CoreUtils {
>
> public static boolean anotherFunction() {
> System.out.println("anotherFunction() inside CoreUtils");
> return true;
> }
>
> public static boolean anotherFunction(SampleDomain sampleDomain) {
> System.out.println("anotherFunction(SampleDomain sampleDomain) inside CoreUtils");
> return true;
> }
> }
> {code}
> My domain file is:
> {code:java}
> public class SampleDomain {
> private int instanceVariable1;
> private String instanceVariable2;
> private int instanceVariable3;
>
>
> public int getInstanceVariable1() {
> return instanceVariable1;
> }
> public void setInstanceVariable1(int instanceVariable1) {
> this.instanceVariable1 = instanceVariable1;
> }
> public String getInstanceVariable2() {
> return instanceVariable2;
> }
> public void setInstanceVariable2(String instanceVariable2) {
> this.instanceVariable2 = instanceVariable2;
> }
> public int getInstanceVariable3() {
> return instanceVariable3;
> }
> public void setInstanceVariable3(int instanceVariable3) {
> this.instanceVariable3 = instanceVariable3;
> }
>
>
> }
> {code}
> This is only caused after version change from `7.20.0.Final` to `7.21.0.Final`. Any guess on what the problem might be?
> When I further looked into the problem I saw this too.
> When we add two functions into the `SampleDomain` class ie
> {code:java}
> public boolean anotherFunction() {
> return true;
> }
>
> public boolean anotherFunction(SampleDomain sampleDomain) {
> return true;
> }
> {code}
> and use this in the rule like:
> {code:java}
> rule "rule 1.4"
> when
> $sampleDomain: SampleDomain(anotherFunction())
> then
> System.out.println("Rule 1.4 fired");
> modify($sampleDomain){
> setInstanceVariable1(3)
> }
> end
> {code}
> and
> {code:java}
> rule "rule 1.5"
> when
> $sampleDomain: SampleDomain(anotherFunction($sampleDomain))
> then
> System.out.println("Rule 1.5 fired");
> modify($sampleDomain){
> setInstanceVariable3(4)
> }
> end
> {code}
> these also loops recursively.
> *Code in github:*
> [The recursive looping when using non static methods|https://github.com/padippist/DroolsIssueReporting/tree/issue_v_7....]
> [The change between working and above version|https://github.com/padippist/DroolsIssueReporting/compare/issue_v...]
> Also when any of the static method is made non static then method from the domain class is called even though the static method is specified in the rule.
> *Code portions to be noted here are:*
> [Rule where static method is called.|https://github.com/padippist/DroolsIssueReporting/blob/bde2804b25...]
> [Another rule which also call the static method.|https://github.com/padippist/DroolsIssueReporting/blob/bde2804b25...]
> [The static access modifier removed from the functions which where previously static.|https://github.com/padippist/DroolsIssueReporting/compare/issue_v...]
> *Code in github:*
> [Weird behaviour when removing static modifier for the functions.|https://github.com/padippist/DroolsIssueReporting/tree/issue_v...]
> [The change between working and above version|https://github.com/padippist/DroolsIssueReporting/compare/issue_v...]
> *All this are caused in versions after `7.20.0.Final`, ie `7.21.0.Final`, `7.22.0.Final` and `7.23.0.Final`*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (DROOLS-4363) Improve the comprehensive Readme
by Massimiliano Dessi (Jira)
Massimiliano Dessi created DROOLS-4363:
------------------------------------------
Summary: Improve the comprehensive Readme
Key: DROOLS-4363
URL: https://issues.jboss.org/browse/DROOLS-4363
Project: Drools
Issue Type: Task
Reporter: Massimiliano Dessi
Assignee: Massimiliano Dessi
Improve the readme in the @TODO sections , with feedbacks and with a Drools sections
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (SWSQE-847) 3scale Adapter - Identify Tester Resource
by Matthew Mahoney (Jira)
Matthew Mahoney created SWSQE-847:
-------------------------------------
Summary: 3scale Adapter - Identify Tester Resource
Key: SWSQE-847
URL: https://issues.jboss.org/browse/SWSQE-847
Project: Kiali QE
Issue Type: QE Task
Reporter: Matthew Mahoney
Assignee: Michael Foley
Currently there is no test coverage for 3scale Adapter. The purpose of this task is to identify a 3scale Adapter tester resource.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months
[JBoss JIRA] (JGRP-2365) Class cast exception when upgrading from 4.0.20 to 4.1.0 or 4.1.1
by Bernd Laengerich (Jira)
Bernd Laengerich created JGRP-2365:
--------------------------------------
Summary: Class cast exception when upgrading from 4.0.20 to 4.1.0 or 4.1.1
Key: JGRP-2365
URL: https://issues.jboss.org/browse/JGRP-2365
Project: JGroups
Issue Type: Bug
Affects Versions: 4.1.1, 4.1.0
Reporter: Bernd Laengerich
Assignee: Bela Ban
Attachments: fork-stacks.xml, tcp_fork.xml
Updating from 4.0.20 to 4.1.1 I get
"java.lang.ClassCastException: org.jgroups.protocols.CENTRAL_LOCK cannot be cast to org.jgroups.protocols.TP"
when creating a JChannel using the same config as before. My config is [^tcp_fork.xml] attached to this issue. The stack trace:
{noformat}
java.lang.ClassCastException: org.jgroups.protocols.CENTRAL_LOCK cannot be cast to org.jgroups.protocols.TP
at org.jgroups.stack.Configurator.createProtocolsAndInitializeAttrs(Configurator.java:110) ~[jgroups-4.1.1.Final.jar:4.1.1.Final]
at org.jgroups.protocols.FORK.createForkStacks(FORK.java:273) ~[jgroups-4.1.1.Final.jar:4.1.1.Final]
at org.jgroups.protocols.FORK.createForkStacks(FORK.java:265) ~[jgroups-4.1.1.Final.jar:4.1.1.Final]
at org.jgroups.protocols.FORK.init(FORK.java:100) ~[jgroups-4.1.1.Final.jar:4.1.1.Final]
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:857) ~[jgroups-4.1.1.Final.jar:4.1.1.Final]
at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:480) ~[jgroups-4.1.1.Final.jar:4.1.1.Final]
at org.jgroups.JChannel.init(JChannel.java:952) ~[jgroups-4.1.1.Final.jar:4.1.1.Final]
at org.jgroups.JChannel.<init>(JChannel.java:125) ~[jgroups-4.1.1.Final.jar:4.1.1.Final]
at org.jgroups.JChannel.<init>(JChannel.java:107) ~[jgroups-4.1.1.Final.jar:4.1.1.Final]
at com.acceptis.accept.jgroups.config.JGroupsConfigurator.setConfiguration(JGroupsConfigurator.java:86) [main/:?]
at com.acceptis.framework.locking.impl.test.JGroupsLockManagerTest.setUp(JGroupsLockManagerTest.java:40) [test/:?]
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 12 months