August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4449) Visual design enhancements: Scenario/DMN error overlays

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4449?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4449: -------------------------------------- Sprint: 2019 Week 35-37 > Visual design enhancements: Scenario/DMN error overlays > ------------------------------------------------------- > > Key: DROOLS-4449 > URL: https://issues.jboss.org/browse/DROOLS-4449 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor, Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Brian Dellascio > Priority: Major > Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools > > Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context. > Verification conditions: > - Review interaction design wireframes and click-thrus to offer recommendations for a consistent presentation for error overlays for the two editors (Scenario and DMN) > - Wireframes posted at: https://issues.jboss.org/browse/DROOLS-4257 and https://issues.jboss.org/browse/DROOLS-3953. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4410) [DMN Designer] Search feature - DMN/GDT (7.7)

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4410?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4410: ------------------------------------ Summary: [DMN Designer] Search feature - DMN/GDT (7.7) (was: [DMN Designer] Search feature - DMN/GDT (7.6)) Epic Name: [DMN Designer] Search feature - DMN/GDT (7.7) (was: [DMN Designer] Search feature - DMN/GDT (7.6)) > [DMN Designer] Search feature - DMN/GDT (7.7) > --------------------------------------------- > > Key: DROOLS-4410 > URL: https://issues.jboss.org/browse/DROOLS-4410 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs (target to 7.6) related to the Search feature feature. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4412) [DMN Designer] Improve the Data Types support (7.7)

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4412?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4412: ------------------------------------ Summary: [DMN Designer] Improve the Data Types support (7.7) (was: [DMN Designer] Improve the Data Types support (7.6)) Epic Name: [DMN Designer] Improve the Data Types support (7.7) (was: [DMN Designer] Improve the Data Types support (7.6)) > [DMN Designer] Improve the Data Types support (7.7) > --------------------------------------------------- > > Key: DROOLS-4412 > URL: https://issues.jboss.org/browse/DROOLS-4412 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs (target to 7.6) related to enhancements on Data Types. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4411) [DMN Designer] Included Models (7.7)

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4411?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4411: ------------------------------------ Summary: [DMN Designer] Included Models (7.7) (was: [DMN Designer] Included Models (7.6)) Epic Name: [DMN Designer] Included Models (7.7) (was: [DMN Designer] Included Models (7.6)) > [DMN Designer] Included Models (7.7) > ------------------------------------ > > Key: DROOLS-4411 > URL: https://issues.jboss.org/browse/DROOLS-4411 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs (target to 7.6) related to the Included Models feature. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13

by Gail Badner (Jira)

[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ] Gail Badner commented on WFLY-12063: ------------------------------------ [~brian.stansberry], I can do the upgrade before 9/13. > ClassFormatError on JDK13 > ------------------------- > > Key: WFLY-12063 > URL: https://issues.jboss.org/browse/WFLY-12063 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Richard Opalka > Assignee: Scott Marlow > Priority: Critical > Labels: blocker-WF18 > Attachments: server.log, test.log > > > The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly. > Affected tests are: > --- > [ERROR] Errors: > [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment > [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment > [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment > [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment > [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment > [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy... > [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment > [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment > [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment > [INFO] > [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14 > --- -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFWIP-181?page=com.atlassian.jira.plugin.... ] James Perkins reassigned WFWIP-181: ----------------------------------- Assignee: Cheng Fang (was: James Perkins) > Access logging for EJBs: no logs produced > ----------------------------------------- > > Key: WFWIP-181 > URL: https://issues.jboss.org/browse/WFWIP-181 > Project: WildFly WIP > Issue Type: Bug > Components: Logging > Reporter: Tommasso Borgato > Assignee: Cheng Fang > Priority: Blocker > > File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs; > As specified in the RFE, the server is reloaded after changes; > We verified that with the following: > {noformat} > <access-log> > <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir"> > <formatter name="p1"/> > </file-handler> > <formatter> > <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/> > </formatter> > </access-log> > {noformat} > or > {noformat} > <access-log> > <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir"> > <formatter name="p1"/> > </file-handler> > <formatter> > <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/> > </formatter> > </access-log> > {noformat} > : no file {{standalone/log/ejb-access.log}} is produced; > {noformat} > <access-log> > <server-log-handler name="server1"> > <formatter name="p1"/> > </server-log-handler> > <formatter> > <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/> > </formatter> > </access-log> > {noformat} > or > {noformat} > <access-log> > <server-log-handler name="server1"> > <formatter name="p1"/> > </server-log-handler> > <formatter> > <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/> > </formatter> > </access-log> > {noformat} > : no logs in {{standalone/log/server.log}}; > {noformat} > <access-log> > <console-handler name="console1"> > <formatter name="p1"/> > </console-handler> > <formatter> > <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/> > </formatter> > </access-log> > {noformat} > : no logs in console; -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4475) Executable model doesn't generate stable ids for indexes across different compilations

by Mario Fusco (Jira)

Mario Fusco created DROOLS-4475: ----------------------------------- Summary: Executable model doesn't generate stable ids for indexes across different compilations Key: DROOLS-4475 URL: https://issues.jboss.org/browse/DROOLS-4475 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-178) [Galleon] Script fails when JGROUPS_CLUSTER_PASSWORD is set by template

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-178?page=com.atlassian.jira.plugin.... ] Jean Francois Denise commented on WFWIP-178: -------------------------------------------- [~mjurc], the chained build is not in the context of this issue. We have existing template that consider the EAP server to contain a complete configuration. When using galleon we can't guarantee that the provisioned server will contain it all. For example jgroups will be not present when provisioning a cloud-profile. With respect to chained build and legacy templates, you should log a new issue, something like "Existing EAP templates are not taking benefit of chained builds". > [Galleon] Script fails when JGROUPS_CLUSTER_PASSWORD is set by template > ----------------------------------------------------------------------- > > Key: WFWIP-178 > URL: https://issues.jboss.org/browse/WFWIP-178 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Nikoleta Ziakova > Assignee: Jean Francois Denise > Priority: Blocker > > Steps to reproduce: > # Provision server without jgroups subsystem, e.g. https://github.com/nziakova/jboss-eap-quickstarts/tree/with_galleon_dir/k... > # Use [template|https://github.com/jboss-container-images/jboss-eap-7-openshift-...] to deploy the application > The template sets default {{JGROUPS_CLUSTER_PASSWORD}} which causes the scripts fail: > {code} > ERROR "Cannot configure the jgroups authentication. The jgroups subsystem is not present in the server configuration file." > {code} > It must be decided whether it is a bug in scripts or templates. Updating the templates would cause backwards compatibility issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ] Scott Marlow edited comment on WFLY-12063 at 8/26/19 12:09 PM: --------------------------------------------------------------- Oh, then that is fine then! :) I did run a lot of WF unit tests locally already as well [https://issues.jboss.org/browse/WFLY-12063?focusedCommentId=13757425&page...] [https://github.com/wildfly/wildfly/pull/12533] is the pr for testing was (Author: smarlow): Oh, then that is fine then! :) I did run a lot of WF unit tests locally already as well [https://issues.jboss.org/browse/WFLY-12063?focusedCommentId=13757425&page...] > ClassFormatError on JDK13 > ------------------------- > > Key: WFLY-12063 > URL: https://issues.jboss.org/browse/WFLY-12063 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Richard Opalka > Assignee: Scott Marlow > Priority: Critical > Labels: blocker-WF18 > Attachments: server.log, test.log > > > The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly. > Affected tests are: > --- > [ERROR] Errors: > [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment > [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment > [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment > [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment > [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment > [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy... > [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment > [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment > [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment > [INFO] > [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14 > --- -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3710) HA CEP Kafka

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3710?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-3710. ---------------------------------------- Release Notes Text: Release for 7.5 (was: Replaced by https://issues.jboss.org/browse/DROOLS-4337) Resolution: Done > HA CEP Kafka > ------------- > > Key: DROOLS-3710 > URL: https://issues.jboss.org/browse/DROOLS-3710 > Project: Drools > Issue Type: Epic > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > > All the steps are described here https://docs.google.com/document/d/1Wt-lHm1BTRbgX8okCcjDZSLEaE34WP4sgqMfC... > https://github.com/desmax74/openshift-drools-hacep -- This message was sent by Atlassian Jira (v7.12.1#712002)

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