January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1982) Test Scenarios: User should be able to compare lists in expect section

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1982?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-1982. -------------------------------- Resolution: Won't Do > Test Scenarios: User should be able to compare lists in expect section > ---------------------------------------------------------------------- > > Key: DROOLS-1982 > URL: https://issues.jboss.org/browse/DROOLS-1982 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Attachments: shouldWork.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1983) Its possible to leave the "Expect rule to fire" field empty in test scenarios

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1983?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-1983. -------------------------------- Resolution: Won't Do > Its possible to leave the "Expect rule to fire" field empty in test scenarios > ----------------------------------------------------------------------------- > > Key: DROOLS-1983 > URL: https://issues.jboss.org/browse/DROOLS-1983 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Minor > > Add new expect to test scenario. > Instead of typing a rule name or selecting one from the dropdown, clik ok-button on that row. > Creates a broken expect that does nothing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1986) Issue with Date format while running test scenario

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1986?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-1986. -------------------------------- Resolution: Explained New Test Scenarios editor will be better. > Issue with Date format while running test scenario > -------------------------------------------------- > > Key: DROOLS-1986 > URL: https://issues.jboss.org/browse/DROOLS-1986 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Environment: Guvnor 5.2 and 5.3 on Linux > Reporter: Alex N > Assignee: Toni Rikkola > Priority: Major > > The test scenario fails when comparing dates in the Expects section. The test scenario has date in format dd-MMM-yyyy while the value returned by the rule is in java.util.Date format e.g. Thu Apr 24 00:00:00 EST 1975. Hence the assertion birthDate equals 24-Apr-1975 fails while running the test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1986) Issue with Date format while running test scenario

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1986?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-1986: -------------------------------------- Sorry [~rampageido] you waited all these years and now I'm here to reject this. > Issue with Date format while running test scenario > -------------------------------------------------- > > Key: DROOLS-1986 > URL: https://issues.jboss.org/browse/DROOLS-1986 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Environment: Guvnor 5.2 and 5.3 on Linux > Reporter: Alex N > Assignee: Toni Rikkola > Priority: Major > > The test scenario fails when comparing dates in the Expects section. The test scenario has date in format dd-MMM-yyyy while the value returned by the rule is in java.util.Date format e.g. Thu Apr 24 00:00:00 EST 1975. Hence the assertion birthDate equals 24-Apr-1975 fails while running the test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-158) Unauthorized access exception when closing JMX console and RBAC is set on server

by Brad Maxwell (Jira)

[ https://issues.jboss.org/browse/REMJMX-158?page=com.atlassian.jira.plugin... ] Brad Maxwell reassigned REMJMX-158: ----------------------------------- Assignee: Brad Maxwell (was: Richard Opalka) > Unauthorized access exception when closing JMX console and RBAC is set on server > -------------------------------------------------------------------------------- > > Key: REMJMX-158 > URL: https://issues.jboss.org/browse/REMJMX-158 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Reporter: Richard Opalka > Assignee: Brad Maxwell > Priority: Major > Fix For: 3.1.0.Beta1 > > > javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1204) > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1190) > at org.jboss.as.jmx.PluggableMBeanServerImpl.removeNotificationListener(PluggableMBeanServerImpl.java:946) > at org.jboss.as.jmx.BlockingNotificationMBeanServer.removeNotificationListener(BlockingNotificationMBeanServer.java:243) > at org.jboss.as.jmx.AuthorizingMBeanServer.removeNotificationListener(AuthorizingMBeanServer.java:352) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListener(ServerProxy.java:229) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListeners(ServerProxy.java:239) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListener(ServerProxy.java:222) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.access$1900(ServerProxy.java:199) > at org.jboss.remotingjmx.protocol.v2.ServerProxy.end(ServerProxy.java:167) > at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever.handleEnd(ServerCommon.java:216) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$notifyEnd$0(RemoteConnectionChannel.java:291) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:957) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1987) [Test Scenario] Rules are not loaded into 'New expectation' dialogue

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1987?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-1987. -------------------------------- Resolution: Out of Date Works now. > [Test Scenario] Rules are not loaded into 'New expectation' dialogue > -------------------------------------------------------------------- > > Key: DROOLS-1987 > URL: https://issues.jboss.org/browse/DROOLS-1987 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: dtable_testday_preparation, qe-suggest-pre-7.0.0.Final, qe-test-day, reported-by-qe > > There is *(show list)* button in the *New expectation* dialogue. This button should show list of rules available in the current package. However my rules from the same package are not loaded. For more details, please see steps to reproduce. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4273) Layers for core-galleon-pack

by Jean-Francois Denise (Jira)

Jean-Francois Denise created WFCORE-4273: -------------------------------------------- Summary: Layers for core-galleon-pack Key: WFCORE-4273 URL: https://issues.jboss.org/browse/WFCORE-4273 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise In order to take benefit from galleon layers feature, the core galleon feature-pack should define layers that could then be used to build custom installation. The layers are not intended to be exposed as a public contract, they are an implementation detail allowing for internal custom provisioning. We are proposing: 1) Define a set of core layers that target standalone kind of configurations. Layers have no dependency on legacy security realms, security aspects are handled using elytron. Patching is also not covered by layers. List of layers: base-server core-management deployment-scanner discovery elytron io jmx jmx-remoting logging management secure-management remoting request-controller security-manager core-server (aggregation of base-server, elytron, secure-management, jmx, jmx-remoting, logging, core-management, request-controller, security-manager) core-tools (all core management tools). 2) Express the default standalone configuration by a set of layers. The default configuration based on layers would be identical to the current one (based on feature-groups). feature-groups are the place where feature configuration occurs, layers are referencing feature-groups. The default configuration extends layers with legacy security aspects. 3) domain kind of configurations are not impacted by layers. 4) In order for galleon to be able to only provision the set of modules required by layers and not provision all server's modules, the management API must evolve for server and extensions to express dependencies on modules that are not part of their module.xml required dependencies (eg: modules that are injected in Deployment units). 5) This management API would then be used by server and subsystems. The impacted core resources are root-resource, elytron, jmx, remoting and logging. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1988) Test scenarios not working with ruleflow-group

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1988?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1988: --------------------------------- Component/s: Scenario Simulation and Testing > Test scenarios not working with ruleflow-group > ---------------------------------------------- > > Key: DROOLS-1988 > URL: https://issues.jboss.org/browse/DROOLS-1988 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing, Test Scenarios Editor > Affects Versions: 6.3.0.Beta2 > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > > https://groups.google.com/forum/#!topic/drools-usage/XcHpSeGr8eE -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1990) Test Scenarios: Editor not allowing selection from variable for field value, then corrupts value that I entered as literal after successful test run

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1990?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-1990. -------------------------------- Resolution: Explained There will be a new test scenario editor to replace this editor. > Test Scenarios: Editor not allowing selection from variable for field value, then corrupts value that I entered as literal after successful test run > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1990 > URL: https://issues.jboss.org/browse/DROOLS-1990 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Environment: Guvnor running under Tomcat (7, I think) on Windows XP dual core. Guvnor accessed via Firefox 3.x. > Reporter: Chris Clark > Assignee: Toni Rikkola > Priority: Major > > I have an object mode written in Java and imported as a JAR file. The model contains the following (actual class names changed for clarity): > interface FlyweightIndicator > { > String getCode(); > void setCode(String); // I'd prefer not to have this, but needed it for setting up my test case > } > abstract class AbstractFlyweightIndicator implements FlyweightIndicator > { > String code; > // basic implementations for get/set Code > } > class ConcreteFlyweight extends AbstractFlyweightIndicator > { > ConcreteFlyweight() > { > code = "Something"; > } > } > class ReferencingClass > { > private FlyweightIndicator myInd; > // standard implementations for get/set myInd > // some other properties, some primitives, mostly Objects > } > I have a rule which which is supposed to fire when there is a ReferecingClass that has myInd set to a specific flyweight object. > When I went to code the test case, I created a GIVEN instance of the ConcreteFlyweightClass [$fly] (and had to set the code, the constructor didn't seem to get called to set it?). > Then I created another GIVEN for the ReferencingClass [$ref]. I added the myInd field. > Problem #1 > Is that the editor won't give me the option to bind $fly to the field. I only get a text box. > So I typed in "=$fly". > The test case ran and it passed. Typing in $fly seems to have done what I wanted and set the variable. > Problem #2 > Is that after the one successful run, the GIVEN section changed the myInd field to a dropdown, but it didn't include $fly as the value. When I clicked on the arrow beside the dropdown, $fly wasn't listed. So the field is now not set properly and the rule will fail with a null warning. > I could live with having to type =$fly into the text box, although it should ideally allow me to bind to the variable. But having that removed and replaced with an empty dropdown makes the text case unusable. :( -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1998) Guvnor Test Scenarios - "unable to find constructor" error using a Java Interface in the Facts model

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1998?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-1998. -------------------------------- Resolution: Explained This editor is being replaced by the new table based test scenarios editor. > Guvnor Test Scenarios - "unable to find constructor" error using a Java Interface in the Facts model > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1998 > URL: https://issues.jboss.org/browse/DROOLS-1998 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Environment: Mac OS X version 10.5.8, jboss 4.2.3, jdk_1.6 > Reporter: Alessandra Magenta > Assignee: Toni Rikkola > Priority: Major > Labels: Test > Attachments: Sales.java, SalesImpl.java, repository_export.xml > > > If I use some Facts with a Java Interface I have an error on running Test Scenarios like: > There was an error executing the consequence of rule [SalesRule] > rule: SalesRule CAUSED BY [Error: unable to find constructor: Sales()] [Near : {... Unknown ....}] ^ [Line: 1, Column: 0] > I have a Java class SalesImpl that implement the Sale Interface > How I can resolve this error? -- 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 January 2019