October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4681) [DMN Designer] Data Types - Implement the new dropdown design in the type selector

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4681: --------------------------------------- Summary: [DMN Designer] Data Types - Implement the new dropdown design in the type selector Key: DROOLS-4681 URL: https://issues.jboss.org/browse/DROOLS-4681 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Attachments: prototype.png Implement the new dropdown design in the type selector, following the prototype: !prototype.png|width=600! Notice: this JIRA comprehends the tooltip into the label as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4688) '-Xlog:gc' option is not supported on OpenJDK11 + OpenJ9

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4688?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-4688: ------------------------------------------ [~luck3y] FYI. See also https://github.com/wildfly/wildfly-core/pull/3967/commits > '-Xlog:gc' option is not supported on OpenJDK11 + OpenJ9 > -------------------------------------------------------- > > Key: WFCORE-4688 > URL: https://issues.jboss.org/browse/WFCORE-4688 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Jan Stourac > Assignee: James Perkins > Priority: Major > > With OpenJDK11 + OpenJ9, I can see following error during the server bootup: > {code} > JVMJ9VM085W Malformed option: '-Xlog:gc*:file=<JBOSS_HOME_PATH>/standalone/log/gc.log:time' > {code} > Based on the [discussion here|https://github.com/eclipse/openj9/issues/3999], the {{-Xlog:gc}} option is not supported in this JDK and it won't be. > Relevant part of the startup script for standalone.sh in [upstream WildFly|https://github.com/wildfly/wildfly-core/blob/master/core-feature-...]. > This warning occurs only on OpenJDK11 + OpenJ9. This does not show up when using OpenJDK8 + OpenJ9 as different branch in script is used in that case ({{-verbose:gc -Xloggc:\"$JBOSS_LOG_DIR/gc.log\" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading}}). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3566) DMN:Detailed interactions for creating and managing DRDs

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3566?page=com.atlassian.jira.plugi... ] Elizabeth Clayton resolved DROOLS-3566. --------------------------------------- Resolution: Done [~tirelli] I'm marking as Resolved based on review by [~manstis] and [~karreiro], but will demo at the scrum meeting as well to verify. > DMN:Detailed interactions for creating and managing DRDs > -------------------------------------------------------- > > Key: DROOLS-3566 > URL: https://issues.jboss.org/browse/DROOLS-3566 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: contextual-menu.png > > > Canvas node actions related to grouping and assigning to DRDs. > * As a user I want to easily select and group nodes on the canvas so that I can add them to a DRD or to create a new DRD. > (TBD) As a user I want to be able to be able to use the Navigator tree to create DRD's and assign canvas nodes, so that I can easily modify my graph views. > Notes: > Navigator Tree actions TBD: > * Drag nodes to DRDs. > * Contextual menu for tree objects? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12707) Passing the command line properties enforcer.skip or checkstyle.skip override cases where they should be skipped

by James Perkins (Jira)

James Perkins created WFLY-12707: ------------------------------------ Summary: Passing the command line properties enforcer.skip or checkstyle.skip override cases where they should be skipped Key: WFLY-12707 URL: https://issues.jboss.org/browse/WFLY-12707 Project: WildFly Issue Type: Bug Components: Build System Reporter: James Perkins Assignee: James Perkins In some of the tests there is a {{enforcer.skip}} and/or {{checkstyle.skip}} property defined which is overridden if the property is passed on the command line. In these cases the respective plugin should be defined with an explicit {{<skip>true</skip>}} configuration parameter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-170) Support "TIMESTAMP WITH TIME ZONE" for OffsetDateTime and ZonedDateTime

by nimo stephan (Jira)

nimo stephan created HIBERNATE-170: -------------------------------------- Summary: Support "TIMESTAMP WITH TIME ZONE" for OffsetDateTime and ZonedDateTime Key: HIBERNATE-170 URL: https://issues.jboss.org/browse/HIBERNATE-170 Project: Hibernate Integration Issue Type: Enhancement Reporter: nimo stephan Assignee: Steve Ebersole Something like this is supported in JPA 2.2: {code:java} @Column(name = "timestamp") private OffsetDateTime timestamp; {code} However, the offset is NOT persisted in the database even if the database could support it. For example, when using H2 database, then Hibernate could map this "OffsetDateTime" to the sql datatype "TIMESTAMP WITH TIME ZONE" (because H2 supports it) instead of the datatype "TIMESTAMP". Actually, user assumes that when using "OffsetDateTime" with JPA Annotation, JPA maps the offset as well. But this is not the case. Hibernate could also integrate a fallback for databases which does NOT support "TIMESTAMP WITH TIME ZONE". On schema generation, it could create and store something like "OffsetDateTime" or "ZonedDateTime" into two columns to avoid this manual mapping: {code:java} @Column(name = "created_on") private Instant timestamp; @Column(name = "display_offset") private int offset; {code} Hibernate can make use of its own "HibernateCompositeType" to store one property (OffsetDateTime) into two sql columns (timestamp and offset). With the solution above (by using either "TIMESTAMP WITH TIME ZONE" or the fallback), Hibernate/JPA could map the "OffsetDateTime" and "ZonedDateTime" correctly and completely with an offset or timezone. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-986) OCP 4.1 provisioning is failing on get_hostvars_from_server

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-986?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-986. --------------------------------- Resolution: Done Resolved by using 0.27.0 version of openstacksdk > OCP 4.1 provisioning is failing on get_hostvars_from_server > ----------------------------------------------------------- > > Key: SWSQE-986 > URL: https://issues.jboss.org/browse/SWSQE-986 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Reported issue on github - https://github.com/ansible/ansible/issues/63894 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4067) Add before/afterNodeEvaluated to enable monitoring of engine performance

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4067?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4067: -------------------------------- Sprint: 2019 Week 23-25, 2019 Week 44-46 (from Okt 28) (was: 2019 Week 23-25, 2019 Week 41-43 (from Okt 7)) > Add before/afterNodeEvaluated to enable monitoring of engine performance > ------------------------------------------------------------------------ > > Key: DROOLS-4067 > URL: https://issues.jboss.org/browse/DROOLS-4067 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11728) Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous.

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-11728?page=com.atlassian.jira.plugin... ] Alessio Soldano reassigned WFLY-11728: -------------------------------------- Assignee: Ronald Sigal (was: Alessio Soldano) > Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous. > ---------------------------------------------------------------------------- > > Key: WFLY-11728 > URL: https://issues.jboss.org/browse/WFLY-11728 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 15.0.1.Final > Reporter: Andrej Petras > Assignee: Ronald Sigal > Priority: Critical > Labels: Microprofile, resteasy-client > > {noformat} > 09:35:25,936 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: Failed to start service > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec] > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.Validator.validateBeanName(Validator.java:653) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:121) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:119) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) > 09:35:25,941 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"mp-client-1.0.0-SNAPSHOT.war\".WeldStartService" => "Failed to start service > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec]"}} > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AG-130) Add new callback for 'info' messages.

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-130?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro resolved AG-130. ------------------------------ Resolution: Done > Add new callback for 'info' messages. > ------------------------------------- > > Key: AG-130 > URL: https://issues.jboss.org/browse/AG-130 > Project: Agroal > Issue Type: Bug > Components: api, pool > Affects Versions: 1.6 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.7 > > > Some warning messages can create unjustified concerns on users. For that case create a new 'info' method on the listener interface. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-986) OCP 4.1 provisioning is failing on get_hostvars_from_server

by Filip Brychta (Jira)

Filip Brychta created SWSQE-986: ----------------------------------- Summary: OCP 4.1 provisioning is failing on get_hostvars_from_server Key: SWSQE-986 URL: https://issues.jboss.org/browse/SWSQE-986 Project: Kiali QE Issue Type: Bug Reporter: Filip Brychta Assignee: Filip Brychta Reported issue on github - https://github.com/ansible/ansible/issues/63894 -- This message was sent by Atlassian Jira (v7.13.8#713008)

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