September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4536) Test scenarios fails with default values

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4536?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-4536: ------------------------------------- [~Rikkola] hello, I tried your PR but seems int and double have still the same issue, see [^sample.drl] and !Screenshot from 2019-09-16 12-34-12.png|thumbnail! > Test scenarios fails with default values > ---------------------------------------- > > Key: DROOLS-4536 > URL: https://issues.jboss.org/browse/DROOLS-4536 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.25.0.Final > Reporter: Sudhish Nair > Assignee: Toni Rikkola > Priority: Minor > Labels: drools-tools, support > Attachments: Screenshot from 2019-09-16 12-34-12.png, latestjbpmfailed.png, latestjbpmpassed.png, sample.drl > > > In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass. > The issue is always reproducible. > h2. Acceptance test > - Default empty text (/) > - Default int zero (x) > - Default double zero (x) > - Default boolean true (/) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4536) Test scenarios fails with default values

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4536?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4536: -------------------------------- Description: In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass. The issue is always reproducible. h2. Acceptance test - Default empty text (/) - Default int zero (x) - Default double zero (x) - Default boolean true (/) was: In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass. The issue is always reproducible. h2. Acceptance test - Default empty text - Default int zero - Default double zero - Default boolean false > Test scenarios fails with default values > ---------------------------------------- > > Key: DROOLS-4536 > URL: https://issues.jboss.org/browse/DROOLS-4536 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.25.0.Final > Reporter: Sudhish Nair > Assignee: Toni Rikkola > Priority: Minor > Labels: drools-tools, support > Attachments: Screenshot from 2019-09-16 12-34-12.png, latestjbpmfailed.png, latestjbpmpassed.png, sample.drl > > > In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass. > The issue is always reproducible. > h2. Acceptance test > - Default empty text (/) > - Default int zero (x) > - Default double zero (x) > - Default boolean true (/) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4536) Test scenarios fails with default values

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4536?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4536: -------------------------------- Attachment: sample.drl > Test scenarios fails with default values > ---------------------------------------- > > Key: DROOLS-4536 > URL: https://issues.jboss.org/browse/DROOLS-4536 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.25.0.Final > Reporter: Sudhish Nair > Assignee: Toni Rikkola > Priority: Minor > Labels: drools-tools, support > Attachments: Screenshot from 2019-09-16 12-34-12.png, latestjbpmfailed.png, latestjbpmpassed.png, sample.drl > > > In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass. > The issue is always reproducible. > h2. Acceptance test > - Default empty text (/) > - Default int zero (x) > - Default double zero (x) > - Default boolean true (/) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4536) Test scenarios fails with default values

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4536?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4536: -------------------------------- Attachment: Screenshot from 2019-09-16 12-34-12.png > Test scenarios fails with default values > ---------------------------------------- > > Key: DROOLS-4536 > URL: https://issues.jboss.org/browse/DROOLS-4536 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.25.0.Final > Reporter: Sudhish Nair > Assignee: Toni Rikkola > Priority: Minor > Labels: drools-tools, support > Attachments: Screenshot from 2019-09-16 12-34-12.png, latestjbpmfailed.png, latestjbpmpassed.png, sample.drl > > > In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass. > The issue is always reproducible. > h2. Acceptance test > - Default empty text (/) > - Default int zero (x) > - Default double zero (x) > - Default boolean true (/) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12557) CDI Producer for health check are not supported

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-12557?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-12557: ------------------------------- Priority: Critical (was: Major) > CDI Producer for health check are not supported > ----------------------------------------------- > > Key: WFLY-12557 > URL: https://issues.jboss.org/browse/WFLY-12557 > Project: WildFly > Issue Type: Bug > Components: MP Health > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > > MP Metrics added test for CDI producer in https://github.com/eclipse/microprofile-health/commit/1e8c869c802f78a82e0... that fails with WildFly (when smallrye-health 2.1.5 and microprofile-health 2.1 are integrated) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

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

by Emmanuel Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFWIP-149?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet commented on WFWIP-149: ----------------------------------------- yes > Destination not created 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: Emmanuel 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.13.5#713005)

6 years, 10 months

1
0
0 / 0

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

by Emmanuel Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFWIP-149?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet edited comment on WFWIP-149 at 9/16/19 5:52 AM: ------------------------------------------------------------------ yes it should be marked as resolved was (Author: ehugonnet): yes > Destination not created 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: Emmanuel 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.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4536) Test scenarios fails with default values

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4536?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4536: -------------------------------- Description: In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass. The issue is always reproducible. h2. Acceptance test - Default empty text - Default int zero - Default double zero - Default boolean false was: In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass. The issue is always reproducible. > Test scenarios fails with default values > ---------------------------------------- > > Key: DROOLS-4536 > URL: https://issues.jboss.org/browse/DROOLS-4536 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.25.0.Final > Reporter: Sudhish Nair > Assignee: Toni Rikkola > Priority: Minor > Labels: drools-tools, support > Attachments: latestjbpmfailed.png, latestjbpmpassed.png > > > In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass. > The issue is always reproducible. > h2. Acceptance test > - Default empty text > - Default int zero > - Default double zero > - Default boolean false -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4490) DMN: add a time( hour, minute, second ) alternative signature to the time() function

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4490?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-4490: ------------------------------------------- Fix Version/s: 7.28.0.Final (was: 7.27.0.Final) > DMN: add a time( hour, minute, second ) alternative signature to the time() function > ------------------------------------------------------------------------------------ > > Key: DROOLS-4490 > URL: https://issues.jboss.org/browse/DROOLS-4490 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.26.0.Final > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Priority: Major > Fix For: 7.28.0.Final > > > Add a built in, alternative signature to the time() function: > time( hour, minute, second ) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3907) [DMN Designer] Add visual indicators for imported Nodes

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3907?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-3907: ------------------------------------------- Fix Version/s: 7.28.0.Final (was: 7.27.0.Final) > [DMN Designer] Add visual indicators for imported Nodes > ------------------------------------------------------- > > Key: DROOLS-3907 > URL: https://issues.jboss.org/browse/DROOLS-3907 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, UXTeam, drools-tools > Fix For: 7.28.0.Final > > Attachments: Screen Shot 2019-04-17 at 11.55.39 AM.png, read-only-gridC2.png, read-only-gridC2.png > > > Imported models are read-only. We need to show some form of visual indicator for both Nodes (Graph View) and Boxed Expressions (Grid View). Please see the attachments for proposals for the Grid View. > Design Resolution: > * Option C: https://issues.jboss.org/secure/attachment/12449764/read-only-gridC2.png > * Keeping the hover highlight per row cell as is, because when those elements are clicked the Property panel is updated/reflects. > * Use lock icon for canvas nodes: In the components list and in the graph nodes, as illustrated in: https://issues.jboss.org/secure/attachment/12449758/Screen%20Shot%202019-... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 September 2019