November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3212) Scenario simulation can not be closed without a warning if it has been ran

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3212?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-3212: ------------------------------------------ Check if could be related to FactMappingValue.isError default to null > Scenario simulation can not be closed without a warning if it has been ran > -------------------------------------------------------------------------- > > Key: DROOLS-3212 > URL: https://issues.jboss.org/browse/DROOLS-3212 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Toni Rikkola > Assignee: Gabriele Cardosi > Priority: Major > > The problem is caused by the fact that running the simulation updates the model. > Steps to reproduce: > Open scesim asset. > Run the scenario. > Close the editor > You get a warning that there are unsaved changes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11095) Wildfly 14.0.0 regression: EL returns empty string on constant

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11095?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11095: ----------------------------------------- You're welcome. Thanks for the report! > Wildfly 14.0.0 regression: EL returns empty string on constant > -------------------------------------------------------------- > > Key: WFLY-11095 > URL: https://issues.jboss.org/browse/WFLY-11095 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.0.Final > Environment: Linux > Reporter: Arthur Borsboom > Assignee: Stuart Douglas > Priority: Major > > This does work in Wildfly 13, but not in Wildfly 14: > <%@ page import="com.example.YourConstants" %> > ${YourConstants.FOO} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3212) Scenario simulation can not be closed without a warning if it has been ran

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3212?page=com.atlassian.jira.plugi... ] Gabriele Cardosi reassigned DROOLS-3212: ---------------------------------------- Assignee: Gabriele Cardosi (was: Daniele Zonca) > Scenario simulation can not be closed without a warning if it has been ran > -------------------------------------------------------------------------- > > Key: DROOLS-3212 > URL: https://issues.jboss.org/browse/DROOLS-3212 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Toni Rikkola > Assignee: Gabriele Cardosi > Priority: Major > > The problem is caused by the fact that running the simulation updates the model. > Steps to reproduce: > Open scesim asset. > Run the scenario. > Close the editor > You get a warning that there are unsaved changes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11329) Replace deployment in admin console ignores runtime-name

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11329?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11329: --------------------------------------- Component/s: Web Console Assignee: Harald Pehl (was: Jason Greene) > Replace deployment in admin console ignores runtime-name > --------------------------------------------------------- > > Key: WFLY-11329 > URL: https://issues.jboss.org/browse/WFLY-11329 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 10.1.0.Final > Reporter: Markus Hofmann > Assignee: Harald Pehl > Priority: Minor > > When using the "Add" deployment feature in the admin console, change the runtime name. > When using the "Replace" deployment feature in the admin console, the entered runtime name is ignored and the deployment name is used > Actual results: > The runtime name is set to the same value as deployment name, not the entered runtime name. > Expected results: > The runtime name should not be touched and keep its old runtime name. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11095) Wildfly 14.0.0 regression: EL returns empty string on constant

by Arthur Borsboom (Jira)

[ https://issues.jboss.org/browse/WFLY-11095?page=com.atlassian.jira.plugin... ] Arthur Borsboom commented on WFLY-11095: ---------------------------------------- I will wait for the formal release of Wildfly 15 and give the application I am maintaining another try. Thanks for the friendly info. > Wildfly 14.0.0 regression: EL returns empty string on constant > -------------------------------------------------------------- > > Key: WFLY-11095 > URL: https://issues.jboss.org/browse/WFLY-11095 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.0.Final > Environment: Linux > Reporter: Arthur Borsboom > Assignee: Stuart Douglas > Priority: Major > > This does work in Wildfly 13, but not in Wildfly 14: > <%@ page import="com.example.YourConstants" %> > ${YourConstants.FOO} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11095) Wildfly 14.0.0 regression: EL returns empty string on constant

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11095?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11095: ----------------------------------------- The issues linked to this as duplicates are resolved in 15.0.0.Alpha1, which will probably be renamed to Beta1 and released this week. The 15.0.0.Final is expected at the end of November. > Wildfly 14.0.0 regression: EL returns empty string on constant > -------------------------------------------------------------- > > Key: WFLY-11095 > URL: https://issues.jboss.org/browse/WFLY-11095 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.0.Final > Environment: Linux > Reporter: Arthur Borsboom > Assignee: Stuart Douglas > Priority: Major > > This does work in Wildfly 13, but not in Wildfly 14: > <%@ page import="com.example.YourConstants" %> > ${YourConstants.FOO} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11329) Replace deployment in admin console ignores runtime-name

by Markus Hofmann (Jira)

Markus Hofmann created WFLY-11329: ------------------------------------- Summary: Replace deployment in admin console ignores runtime-name Key: WFLY-11329 URL: https://issues.jboss.org/browse/WFLY-11329 Project: WildFly Issue Type: Bug Affects Versions: 10.1.0.Final Reporter: Markus Hofmann Assignee: Jason Greene When using the "Add" deployment feature in the admin console, change the runtime name. When using the "Replace" deployment feature in the admin console, the entered runtime name is ignored and the deployment name is used Actual results: The runtime name is set to the same value as deployment name, not the entered runtime name. Expected results: The runtime name should not be touched and keep its old runtime name. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-149) Destination not create on remote Artemis broker

by Miroslav Novak (Jira)

Miroslav Novak created WFWIP-149: ------------------------------------ Summary: Destination not create on remote Artemis broker Key: WFWIP-149 URL: https://issues.jboss.org/browse/WFWIP-149 Project: WildFly WIP Issue Type: Bug Components: JMS Reporter: Miroslav Novak Assignee: Jeff Mesnil JMS Destination is not created on remote broker/cluster if activemq-ra resource adapter is configured to connect to it. Test scenario: * Start two servers in Artemis cluster (node-1, node-3) * Start one more server (node-2) which has configured activemq-ra with initial connectors to remote cluster (node-1, node-3) * Deploy MDB with to node-2 with: {code} @JMSConnectionFactoryDefinition( name="java:/jms/myRemoteJmsCf", resourceAdapter="activemq-ra") @JMSDestinationDefinitions({ @JMSDestinationDefinition( name = "java:/jms/queue/myRemoteOutQueue", interfaceName = "javax.jms.Queue", resourceAdapter = "activemq-ra", destinationName = "myRemoteOutQueue"), @JMSDestinationDefinition( name = "java:/jms/queue/myRemoteInQueue", interfaceName = "javax.jms.Queue", resourceAdapter = "activemq-ra", destinationName = "myRemoteInQueue") }) {code} ** MDB resends messages from myRemoteInQueue to myRemoteOutQueue (send using java:/jms/myRemoteJmsCf) * Deploy Servlet to node-2 which uses myRemoteJmsCf to send messages to myRemoteInQueue which are then processed by MDB and re-sent to myRemoteOutQueue Expected result: All messages will be in myRemoteOutQueue Actual result: No message was processed Investigation: Problem is that both of the queues were created on node-2 and not in remote artemis cluster (node-1,3) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-149) Destination not create on remote Artemis broker

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFWIP-149?page=com.atlassian.jira.plugin.... ] Miroslav Novak reassigned WFWIP-149: ------------------------------------ Assignee: ehsavoie Hugonnet (was: Jeff Mesnil) > Destination not create on remote Artemis broker > ----------------------------------------------- > > Key: WFWIP-149 > URL: https://issues.jboss.org/browse/WFWIP-149 > Project: WildFly WIP > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: ehsavoie Hugonnet > Priority: Blocker > > JMS Destination is not created on remote broker/cluster if activemq-ra resource adapter is configured to connect to it. > Test scenario: > * Start two servers in Artemis cluster (node-1, node-3) > * Start one more server (node-2) which has configured activemq-ra with initial connectors to remote cluster (node-1, node-3) > * Deploy MDB with to node-2 with: > {code} > @JMSConnectionFactoryDefinition( > name="java:/jms/myRemoteJmsCf", > resourceAdapter="activemq-ra") > @JMSDestinationDefinitions({ > @JMSDestinationDefinition( > name = "java:/jms/queue/myRemoteOutQueue", > interfaceName = "javax.jms.Queue", > resourceAdapter = "activemq-ra", > destinationName = "myRemoteOutQueue"), > @JMSDestinationDefinition( > name = "java:/jms/queue/myRemoteInQueue", > interfaceName = "javax.jms.Queue", > resourceAdapter = "activemq-ra", > destinationName = "myRemoteInQueue") > }) > {code} > ** MDB resends messages from myRemoteInQueue to myRemoteOutQueue (send using java:/jms/myRemoteJmsCf) > * Deploy Servlet to node-2 which uses myRemoteJmsCf to send messages to myRemoteInQueue which are then processed by MDB and re-sent to myRemoteOutQueue > Expected result: All messages will be in myRemoteOutQueue > Actual result: No message was processed > Investigation: > Problem is that both of the queues were created on node-2 and not in remote artemis cluster (node-1,3) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3313) Avoid double invocation of ScenarioGridPanelProduce.newScenarioGrid()

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3313: ---------------------------------------- Summary: Avoid double invocation of ScenarioGridPanelProduce.newScenarioGrid() Key: DROOLS-3313 URL: https://issues.jboss.org/browse/DROOLS-3313 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Avoid double invocation of "newScenarioGrid" - replace it with PostConstruct/init -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 November 2018