June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4153) Move common code to scenarioeditorpresenter

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4153: ---------------------------------------- Summary: Move common code to scenarioeditorpresenter Key: DROOLS-4153 URL: https://issues.jboss.org/browse/DROOLS-4153 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Move common code/logic from BusinessCentral/Kogit wrappers to SCenarioEditorPresenter -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - error highlight in boxed expression.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Elizabeth Clayton edited comment on DROOLS-3953 at 6/10/19 9:54 AM: -------------------------------------------------------------------- [~zhutaojiajia] Thanks for looking at this, and taking the jira! I was asked to do the error reporting for the graph first, so haven't quite looked at this jira yet. I think [~manstis] might need this one done first: https://issues.jboss.org/browse/DROOLS-3731. WRT clarifying the requirements, [~manstis] [~karreiro] could you comment on what [~danielezonca] mentioned above? ^^ was (Author: uxdlc): [~zhutaojiajia] Thanks for looking at this, and taking the jira! I was asked to do the error reporting for the graph first, so haven't quite looked at this jira yet. I think [~manstis] might need this one done first: https://issues.jboss.org/browse/DROOLS-3731. WRT clarifying the requirements, [~manstis] [~karreiro] that [~danielezonca] commented on above? ^^ > DMN UX - error highlight in boxed expression. > --------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ux-decision button.png, ux-decision table.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - error highlight in boxed expression.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3953: ------------------------------------------- [~zhutaojiajia] Thanks for looking at this, and taking the jira! I was asked to do the error reporting for the graph first, so haven't quite looked at this jira yet. I think [~manstis] might need this one done first: https://issues.jboss.org/browse/DROOLS-3731. WRT clarifying the requirements, [~manstis] [~karreiro] that [~danielezonca] commented on above? ^^ > DMN UX - error highlight in boxed expression. > --------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ux-decision button.png, ux-decision table.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - error highlight in boxed expression.

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3953: --------------------------------------- [~uxdlc] Fine for me to work this item cross team. Btw it is not clear to me the scope of this ticket. It seems to me "a duplicated" of what we already have in scesim. If user wants to analyze the reason of a test failure I don't think he needs the same kind of popover when access to DMN model, I expect he will be interested in see which row of a decision table has been executed etc more than actual/expect value. Actual and expect value are scesim concepts from my point of view > DMN UX - error highlight in boxed expression. > --------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ux-decision button.png, ux-decision table.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12180) In case of registering synchronization via TransactionSynchronizationRegistry for no active transaction context a NPE is thrown

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-12180?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated WFLY-12180: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12356 > In case of registering synchronization via TransactionSynchronizationRegistry for no active transaction context a NPE is thrown > ------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12180 > URL: https://issues.jboss.org/browse/WFLY-12180 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 17.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > Currently when there is a try to register a {{Synchronization}} at place of no active transaction exists then {{NullPointerException}} is thrown. The {{TransactionSynchronizationRegistry.registerInterposedSynchronization(Synchronization sync)}} should throw {{IllegalStateException}} instead (as defined in API of https://javaee.github.io/javaee-spec/javadocs/javax/transaction/Transacti...). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4513) remoting subsystem endpoint does not use specified worker

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4513?page=com.atlassian.jira.plugi... ] Ivo Studensky closed WFCORE-4513. --------------------------------- Resolution: Duplicate Issue This duplicates WFCORE-4510. > remoting subsystem endpoint does not use specified worker > --------------------------------------------------------- > > Key: WFCORE-4513 > URL: https://issues.jboss.org/browse/WFCORE-4513 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Critical > Labels: regression > > remoting subsystem endpoint does not use specified worker > If you reconfigure the server, changing the default io worker name from 'default' to 'thread-pool' and then update all references that used 'default' and start the server, the remoting endpoint is looking for 'default' when it is configured to look for 'thread-pool' > {code} > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "remoting")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.io.worker.default"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.remoting.endpoint is missing [org.wildfly.io.worker.default]"] > {code} > {code} > embed-server > /subsystem=io/worker=mypool:add() > /subsystem=remoting:write-attribute(name=worker, value=mypool) > /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=worker,value=mypool) > /subsystem=undertow/servlet-container=default/setting=websockets:write-attribute(name=worker,value=mypool) > /subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=worker,value=mypool) > /subsystem=io/worker=default:remove() > stop-embed-server > {code} > produces: > {code} > <subsystem xmlns="urn:jboss:domain:io:3.0"> > <worker name="mypool"/> > <buffer-pool name="default"/> > </subsystem> > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <endpoint worker="mypool"/> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/> > </subsystem> > ... > <http-listener name="default" socket-binding="http" worker="mypool" redirect-socket="https" enable-http2="true"/> > <https-listener name="https" socket-binding="https" worker="mypool" security-realm="ApplicationRealm" enable-http2="true"/> > ... > <servlet-container name="default"> > <jsp-config/> > <websockets worker="mypool"/> > </servlet-container> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11608) Improve validation of MDB activation config properties values

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11608?page=com.atlassian.jira.plugin... ] Brian Stansberry reopened WFLY-11608: ------------------------------------- Reopening so I can manipulate issue state. > Improve validation of MDB activation config properties values > ------------------------------------------------------------- > > Key: WFLY-11608 > URL: https://issues.jboss.org/browse/WFLY-11608 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Emmanuel Hugonnet > Assignee: Romain Pelisse > Priority: Major > Fix For: 17.0.0.Beta1 > > > Most of activation config properties values are not validated during MDB deploy. This might lead to successful deployment of misconfigured MDB without any warning. > *Customer scenario*: Customer deploys MDB with misconfigured activation config property(wrong type, unsupported value). MDB deploys without any warning message. However, it doesn't work as expected. In worst case, MDB can not read any message. > *Current validation status* > Values of activation config properties are validated in {{ActiveMQActivationSpec.validate()}} method. Validation covers only 3 scenarios > * not specified destination > * wrong destination type (other than Queue / Topic) > * no subscription name when MDB is durable topic subscriber > Some {{ActiveMQActivationSpec}} properties try to validate supported values in setters. For example {{setAcknowledgeMode()}} throws {{IllegalArgumentException}}. However these exceptions only log message on {{finest}} level, which usually doesn't attract user's attention (see {{BeenUtils.mapJavaBeanProperties}} in {{jboss-common-beans}}) > Other parameters are not validated. > *Possible issues* > Not validated activation config properties can be set to any value without warning. There is a possibility of misconfiguration which can be detected during deploy time. > _Examples_ > Value of {{acknowledgeMode}} can be set to any string or number without warning. If that is the case, server uses default auto acknowledge. However, it doesn't warn user. > If property {{maxSessions}} is configured with negative value, no warning is logged and MDB is unable to consume messages. > If {{destination}} property specifies unknown destination, new destination with provided name is created. User should be informed about that at least on INFO log level (Currently it is debug in {{ActiveMQActivation.setupDestination()}}). > MDB unable to consume messages should not successfully deploy, and user should be informed about the misconfigured values. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11608) Improve validation of MDB activation config properties values

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11608?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-11608. ------------------------------------- Resolution: Done > Improve validation of MDB activation config properties values > ------------------------------------------------------------- > > Key: WFLY-11608 > URL: https://issues.jboss.org/browse/WFLY-11608 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Emmanuel Hugonnet > Assignee: Romain Pelisse > Priority: Major > Fix For: 17.0.0.Beta1 > > > Most of activation config properties values are not validated during MDB deploy. This might lead to successful deployment of misconfigured MDB without any warning. > *Customer scenario*: Customer deploys MDB with misconfigured activation config property(wrong type, unsupported value). MDB deploys without any warning message. However, it doesn't work as expected. In worst case, MDB can not read any message. > *Current validation status* > Values of activation config properties are validated in {{ActiveMQActivationSpec.validate()}} method. Validation covers only 3 scenarios > * not specified destination > * wrong destination type (other than Queue / Topic) > * no subscription name when MDB is durable topic subscriber > Some {{ActiveMQActivationSpec}} properties try to validate supported values in setters. For example {{setAcknowledgeMode()}} throws {{IllegalArgumentException}}. However these exceptions only log message on {{finest}} level, which usually doesn't attract user's attention (see {{BeenUtils.mapJavaBeanProperties}} in {{jboss-common-beans}}) > Other parameters are not validated. > *Possible issues* > Not validated activation config properties can be set to any value without warning. There is a possibility of misconfiguration which can be detected during deploy time. > _Examples_ > Value of {{acknowledgeMode}} can be set to any string or number without warning. If that is the case, server uses default auto acknowledge. However, it doesn't warn user. > If property {{maxSessions}} is configured with negative value, no warning is logged and MDB is unable to consume messages. > If {{destination}} property specifies unknown destination, new destination with provided name is created. User should be informed about that at least on INFO log level (Currently it is debug in {{ActiveMQActivation.setupDestination()}}). > MDB unable to consume messages should not successfully deploy, and user should be informed about the misconfigured values. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11891) Add tests that enable JPA entity class bytecode enhancement

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11891?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-11891. ------------------------------------- Resolution: Done > Add tests that enable JPA entity class bytecode enhancement > ----------------------------------------------------------- > > Key: WFLY-11891 > URL: https://issues.jboss.org/browse/WFLY-11891 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Affects Versions: 16.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Minor > Fix For: 17.0.0.Alpha1 > > Attachments: bytebuddy.log, javassist.log > > > Pick a few unit tests and add the following settings to enable [entity bytecode enhancement|http://docs.jboss.org/hibernate/orm/5.3/userguide/html_single...]: > {code} > <property name="hibernate.enhancer.enableDirtyTracking" value="true"/> > <property name="hibernate.enhancer.enableLazyInitialization" value="true"/> > <property name="hibernate.enhancer.enableAssociationManagement" value="true"/> > {code} > Steps to reproduce: > * Build WildFly > * cd testsuite/integration/basic > * mvn clean install -Dtest=org.jboss.as.test.integration.jpa.transaction.TransactionTestCase > * mvn clean install -Dtest=org.jboss.as.test.integration.jpa.hibernate.management.ManagementTestCase > * mvn clean install -Dtest=org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase > * mvn clean install -Dtest=org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase > Note that the org.jboss.as.test.integration.jpa.transaction.TransactionTestCase test should pass since javassist is specified in the persistence.xml but that seems to be ignored (we still get the ByteBuddy failure). > To workaround failures, prestart wildfly via: ./standalone.sh -Dhibernate.bytecode.provider=javassist and then run tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10340) Enable OpenJPA integration tests for Java 10

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10340?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-10340. ------------------------------------- Resolution: Done > Enable OpenJPA integration tests for Java 10 > -------------------------------------------- > > Key: WFLY-10340 > URL: https://issues.jboss.org/browse/WFLY-10340 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Minor > Fix For: 17.0.0.Alpha1 > > > Disable OpenJPA testing due to WFLY-10177 which reports test failures only on JDK10. When OpenJPA supports Java 10, re-enable org.jboss.as.test.compat.jpa.openjpa.OpenJPASharedModuleProviderTestCase. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 June 2019