August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2900) Implement a static expression builder component

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2900?page=com.atlassian.jira.plugi... ] Gabriele Cardosi resolved DROOLS-2900. -------------------------------------- Resolution: Done > Implement a static expression builder component > ----------------------------------------------- > > Key: DROOLS-2900 > URL: https://issues.jboss.org/browse/DROOLS-2900 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > > Implement a static expression builder component using HTML/CSS proposed in this ticket DROOLS-2784 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2906) Implement scenario runner (backend).

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2906?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2906: --------------------------------- Sprint: 2018 Week 33-35 > Implement scenario runner (backend). > ------------------------------------ > > Key: DROOLS-2906 > URL: https://issues.jboss.org/browse/DROOLS-2906 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10438) Create a domain testsuite test for a missing host-exclude

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-10438?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-10438: -------------------------------- Summary: Create a domain testsuite test for a missing host-exclude (was: Create a domain testsuite smoke test for a missing host-exclude) > Create a domain testsuite test for a missing host-exclude > --------------------------------------------------------- > > Key: WFLY-10438 > URL: https://issues.jboss.org/browse/WFLY-10438 > Project: WildFly > Issue Type: Task > Components: Management, Test Suite > Reporter: Brian Stansberry > Assignee: Yeray Borges > Labels: domain-mode > > We need a simple domain mode smoke test that will fail if a new extension is added without corresponding adjustments to the domain.xml host-exclude resources. > I had a complicated slow approach in mind that I wrote here before; it's stricken out below. > Much simpler approach: > Add a test to testsuite domain that uses a DC running the standard domain.xml. Read from the DC all the extensions. Work through the host-exclude resources. For each host-exclude, take a copy of the set of extensions, remove those listed in the host-exclude and compare the result to a known correct set of extensions for that version. > If we add a new extension and don't host-exclude it, this will fail. This really is all that's needed to avoid completely skipping the host-excludes. > If we add a new host-exclude and don't add the correct set of extensions to the test, the test will fail. This will help ensure the test isn't completely unmaintained. > It doesn't cover people forgetting to add a new legacy version host-exclude when adding the first extension in a new version, but that can be tracked via code review or just being reasonably careful. > Original complicated approach: > -We need a simple test that a slave running the version before the current one can boot and run a minimal server. Basically to catch the need for a fix like WFLY-10396 whenever we add a new extension. > Something like: > Base domain config must be the standard one we ship. It will include all extensions. > Test adds a minimal profile -- bare bones logging subsystem or perhaps no subsystem at all, can only have config that has been legal from the beginning -- and a server group using that profile. The server-group is added to the 'active-server-groups' attribute in the host-exclude resource for the slave's version. > Slave host.xml has 1 server only, and in that server group. > Launch the DC using the current release and the slave using the legacy release. Prove the slave server can start.- -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2906) Implement scenario runner (backend).

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2906?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2906: --------------------------------- Parent: (was: DROOLS-2679) Issue Type: Task (was: Sub-task) > Implement scenario runner (backend). > ------------------------------------ > > Key: DROOLS-2906 > URL: https://issues.jboss.org/browse/DROOLS-2906 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10907) ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-10907: ----------------------------------- Summary: ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException Key: WFLY-10907 URL: https://issues.jboss.org/browse/WFLY-10907 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 14.0.0.Beta2 Reporter: Paul Ferraro Assignee: Paul Ferraro Legacy code will lookup SingletonServiceBuilderFactory using the deprecated ServiceController.awaitValue() or getValue(). This service needs to be installed using the deprecated MSC API, to prevent an UnsupportedOperationException. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1378) Use new API to determine remaining transaction timeout

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1378?page=com.atlassian.jira.plugin... ] Ingo Weiss resolved JBJCA-1378. ------------------------------- Resolution: Done > Use new API to determine remaining transaction timeout > ------------------------------------------------------ > > Key: JBJCA-1378 > URL: https://issues.jboss.org/browse/JBJCA-1378 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.4.9 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > Wildfly transaction manager no longer implements {{TransactionTimeoutConfiguration}}. {{ContextTransactionManager}} API should be used instead to determine remaining transaction timeout. > Related discussions are in https://github.com/wildfly/wildfly-transaction-client/pull/38 and https://issues.jboss.org/browse/WFTC-40 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2676) Input actual data into data fields

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2676?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2676: --------------------------------- Parent: (was: DROOLS-2679) Issue Type: Story (was: Sub-task) > Input actual data into data fields > ---------------------------------- > > Key: DROOLS-2676 > URL: https://issues.jboss.org/browse/DROOLS-2676 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business analyst I want to input actual data into data fields so that I can run a single scenario. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2916) UX design for the contextual menus

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2916?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2916: -------------------------------- Summary: UX design for the contextual menus (was: UX design for the contextual menu) > UX design for the contextual menus > ---------------------------------- > > Key: DROOLS-2916 > URL: https://issues.jboss.org/browse/DROOLS-2916 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > > Provide the labels for the different contextual menus retrieved on right clicking the grid: > 1) click on a "header" cell > 2) click on the first cell of a row > 3) click on any other cell of a row -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2916) UX design for the contextual menu

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2916?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-2916: ------------------------------------- Description: Provide the labels for the different contextual menus retrieved on right clicking the grid: 1) click on a "header" cell 2) click on the first cell of a row 3) click on any other cell of a row > UX design for the contextual menu > --------------------------------- > > Key: DROOLS-2916 > URL: https://issues.jboss.org/browse/DROOLS-2916 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > > Provide the labels for the different contextual menus retrieved on right clicking the grid: > 1) click on a "header" cell > 2) click on the first cell of a row > 3) click on any other cell of a row -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-95) [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFWIP-95?page=com.atlassian.jira.plugin.s... ] Erich Duda closed WFWIP-95. --------------------------- Resolution: Done The issue is fixed. I verified it with WF build from \[1\]. Closing. \[1\] WF_REPO=https://github.com/ehsavoie/wildfly/ WF_BRANCH=WFLY-9407_upgrade_artemis_2.4.0_with_prefix_without_EAP7-673 ARTEMIS_REPO=https://github.com/apache/activemq-artemis/ ARTEMIS_BRANCH=2.6.x > [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names > ----------------------------------------------------------------------------- > > Key: WFWIP-95 > URL: https://issues.jboss.org/browse/WFWIP-95 > Project: WildFly WIP > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq > > Having queue defined as follows > {code:xml} > <jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue" durable="true"/> > {code} > Client is instantiating it directly using its name. > {code:title=Client} > HashMap<String, Object> map = new HashMap<String, Object>(); > map.put("host", hostName); > map.put(TransportConstants.HTTP_UPGRADE_ENABLED_PROP_NAME, true); > map.put("port", httpPort); > TransportConfiguration transportConfiguration = new TransportConfiguration(NettyConnectorFactory.class.getName(), map); > try { > ConnectionFactory cf = ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration); > Queue orderQueue = ActiveMQJMSClient.createQueue("InQueue"); > connection = cf.createConnection(); > session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); > MessageProducer producer = session.createProducer(orderQueue); > connection.start(); > ... > {code} > Client is not able to send messages to, because {{session.createProducer(orderQueue)}} throws following exception > {code} > javax.jms.InvalidDestinationException: Destination InQueue does not exist > at org.apache.activemq.artemis.jms.client.ActiveMQSession.createProducer(ActiveMQSession.java:326) > {code} > This is regression against EAP 7.1.0 > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018