[JBoss JIRA] (DROOLS-2662) Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2662?page=com.atlassian.jira.plugi... ]
Jozef Marko moved RHDM-667 to DROOLS-2662:
------------------------------------------
Project: Drools (was: Red Hat Decision Manager)
Key: DROOLS-2662 (was: RHDM-667)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: Guided Rule Editor
(was: Decision Central)
QE Status: NEW
> Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2662
> URL: https://issues.jboss.org/browse/DROOLS-2662
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Reporter: Jozef Marko
> Assignee: Toni Rikkola
> Attachments: out-15.ogv
>
>
> Consider a Data Object Test with a single field date of type java.time.LocalDate. When using Guided Rule Editor with two different conditions on Test object, with two Test object (the condition are in two separated objects), when we bind the date to a variable the constraint pop up won't open for the other condition, showing an error in console.
> The attached video will clarify the issue.
> That does not seem to happen with built in types and not even with java.util.Date type.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (DROOLS-2662) Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2662?page=com.atlassian.jira.plugi... ]
Jozef Marko reassigned DROOLS-2662:
-----------------------------------
Assignee: Jozef Marko (was: Toni Rikkola)
> Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2662
> URL: https://issues.jboss.org/browse/DROOLS-2662
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Attachments: out-15.ogv
>
>
> Consider a Data Object Test with a single field date of type java.time.LocalDate. When using Guided Rule Editor with two different conditions on Test object, with two Test object (the condition are in two separated objects), when we bind the date to a variable the constraint pop up won't open for the other condition, showing an error in console.
> The attached video will clarify the issue.
> That does not seem to happen with built in types and not even with java.util.Date type.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (DROOLS-2661) Fix blocker findbugs issues
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2661:
-----------------------------------
Summary: Fix blocker findbugs issues
Key: DROOLS-2661
URL: https://issues.jboss.org/browse/DROOLS-2661
Project: Drools
Issue Type: Task
Reporter: Jozef Marko
Assignee: Jozef Marko
In the [report|https://sonarcloud.io/project/issues?id=org.drools%3Adrools-wb&resolved=false&severities=BLOCKER&types=BUG] can be seen blocker issues revealed by the finbugs in the drools-wb repository. The issues are caused by not closed InputStreams. ALl could be fixed by try-with-resources.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2253:
--------------------------------
OK. *If* termination is guaranteed to close sockets, then re-open this issue, and I'll investigate.
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
> Fix For: 4.0.13
>
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (WFLY-10585) BanTransitiveDependencies enforcer violations while building wildfly-galleon-pack module on IBM jdk
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10585?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-10585:
---------------------------------------
Hi [~kabirkhan], I can verify that fix solves the problem.
{noformat}
$ git rev-parse --short HEAD
cf8f1bf1e2
$ mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
Maven home: /usr/lib/maven
Java version: 1.8.0_171, vendor: IBM Corporation
Java home: /usr/lib/java/ibm-java-8.0-5.16/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.16.15-300.fc28.x86_64", arch: "amd64", family: "unix"
$ mvn package -pl galleon-pack
...
[INFO] BUILD SUCCESS
{noformat}
> BanTransitiveDependencies enforcer violations while building wildfly-galleon-pack module on IBM jdk
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-10585
> URL: https://issues.jboss.org/browse/WFLY-10585
> Project: WildFly
> Issue Type: Bug
> Components: Build System, Web Services
> Reporter: Petr Kremensky
> Assignee: R Searls
> Fix For: 14.0.0.CR1
>
>
> Building WildFly: Full Galleon Pack using IBM jdk fails with enforcer BanTransitiveDependencies violation.
> *reproduce*
> {noformat}
> wildfly] $ mvn package -pl galleon-pack
> ...
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (ban-transitive-deps) @ wildfly-galleon-pack ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
> org.wildfly:wildfly-galleon-pack:pom:14.0.0.Beta1-SNAPSHOT
> org.apache.cxf:cxf-rt-features-logging:jar:3.2.4-jbossorg-1:compile has transitive dependencies:
> xalan:xalan:jar:2.7.1.jbossorg-4:compile
> xalan:serializer:jar:2.7.1.jbossorg-4:compile
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 21.949 s
> [INFO] Finished at: 2018-06-18T13:30:17+02:00
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (ban-transitive-deps) on project wildfly-galleon-pack: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
> {noformat}
> *workaround*
> Skip enforcer by adding {{-Denforcer.skip=true}} property
> *environment*
> {noformat}
> $ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_171, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.16/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.16.15-300.fc28.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> 4eff06230b
> {noformat}
> *ibm jdk download*
> https://developer.ibm.com/javasdk/downloads/sdk8/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer
by Gail Badner (JIRA)
[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ]
Gail Badner commented on WFLY-10520:
------------------------------------
[~sgilda], the Migration Guide for sure. As far as how the transformer gets enabled, I think that would go in the WF documentation.
[~smarlow], WDYT?
> Add Hibernate ORM 5.3 compatibility transformer
> -----------------------------------------------
>
> Key: WFLY-10520
> URL: https://issues.jboss.org/browse/WFLY-10520
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate
> Reporter: Gail Badner
> Assignee: Scott Marlow
> Fix For: 14.0.0.CR1
>
>
> A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1.
> From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w...
> # Change call to org.hibernate.BasicQueryContract.getFlushMode() to instead call BasicQueryContract.getHibernateFlushMode().
> # Change call to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode()
> # App References to Enum org.hibernate.FlushMode.NEVER (0) should be transformed to reference FlushMode.MANUAL (0) instead.
> # For call to org.hibernate.Query.getMaxResults() returning Integer, instead call org.hibernate.Query.getHibernateMaxResults() (returning Integer).
> # For call to org.hibernate.Query.setMaxResults(int), instead call org.hibernate.Query.setHibernateMaxResults(int).
> # For call to org.hibernate.Query.getFirstResult(int) returning Integer, instead call org.hibernate.Query.getHibernateFirstResult() (returning Integer).
> # For call to org.hibernate.Query.setFirstResult(int), instead call org.hibernate.Query.setHibernateFirstResult(int).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months
[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2656:
----------------------------------------
[~bdellasc] I am already using some temporary PNGs (copied from the BPMN toolbox icon-set) :-)
> PNGs for the toolbox icons for the different connector types.
> -------------------------------------------------------------
>
> Key: DROOLS-2656
> URL: https://issues.jboss.org/browse/DROOLS-2656
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Brian Dellascio
> Labels: UX, UXTeam, VisualDesign
>
> PNGs for the toolbox icons for the different connector types.
> Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 11 months