June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4155) [DMN Designer] Placeholder doesn't fit a column

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4155?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4155: -------------------------------- Description: If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. h3. Acceptance test - Function column width, resizeable - Change Expression type to Function - Change Function Type - Undo function column width resize - Decision > Context > Function column width, resizeable - BKM > Function column width, resizeable was: If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. h3. Acceptance test - Function column width, resizeable - Change Expression type to Function - Undo function column width resize - Decision > Context > Function column width, resizeable - BKM > Function column width, resizeable > [DMN Designer] Placeholder doesn't fit a column > ----------------------------------------------- > > Key: DROOLS-4155 > URL: https://issues.jboss.org/browse/DROOLS-4155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: placeholder.png > > > If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. > h3. Acceptance test > - Function column width, resizeable > - Change Expression type to Function > - Change Function Type > - Undo function column width resize > - Decision > Context > Function column width, resizeable > - BKM > Function column width, resizeable -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4155) [DMN Designer] Placeholder doesn't fit a column

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4155?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4155: -------------------------------- Description: If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. h3. Acceptance test - Function column width, resizeable - Change Expression type to Function - Change Function Type (FEEL / JAVA / PMML) - Undo function column width resize - Decision > Context > Function column width, resizeable - BKM > Function column width, resizeable was: If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. h3. Acceptance test - Function column width, resizeable - Change Expression type to Function - Change Function Type - Undo function column width resize - Decision > Context > Function column width, resizeable - BKM > Function column width, resizeable > [DMN Designer] Placeholder doesn't fit a column > ----------------------------------------------- > > Key: DROOLS-4155 > URL: https://issues.jboss.org/browse/DROOLS-4155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: placeholder.png > > > If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. > h3. Acceptance test > - Function column width, resizeable > - Change Expression type to Function > - Change Function Type (FEEL / JAVA / PMML) > - Undo function column width resize > - Decision > Context > Function column width, resizeable > - BKM > Function column width, resizeable -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4155) [DMN Designer] Placeholder doesn't fit a column

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4155?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4155: -------------------------------- Description: If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. h3. Acceptance test - Function column width, resizeable - Change Expression type to Function - Undo function column width resize - Decision > Context > Function column width, resizeable - BKM > Function column width, resizeable was:If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. > [DMN Designer] Placeholder doesn't fit a column > ----------------------------------------------- > > Key: DROOLS-4155 > URL: https://issues.jboss.org/browse/DROOLS-4155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: placeholder.png > > > If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. > h3. Acceptance test > - Function column width, resizeable > - Change Expression type to Function > - Undo function column width resize > - Decision > Context > Function column width, resizeable > - BKM > Function column width, resizeable -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4155) [DMN Designer] Placeholder doesn't fit a column

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4155?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4155: -------------------------------- Tester: Jozef Marko (was: Yevgeniy Fomin) > [DMN Designer] Placeholder doesn't fit a column > ----------------------------------------------- > > Key: DROOLS-4155 > URL: https://issues.jboss.org/browse/DROOLS-4155 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: placeholder.png > > > If user included a *PMML* model into a DMN diagram, then he has possibility to define PMML function invocation. Grid for such invocation contains placeholders saying that document and model needs to be specified. The issue is placeholders doesn't column width and thus are not readable. See the attached picture. > h3. Acceptance test > - Function column width, resizeable > - Change Expression type to Function > - Undo function column width resize > - Decision > Context > Function column width, resizeable > - BKM > Function column width, resizeable -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4518) Ensure the ServiceTarget is stable for the subsystem test KernelServices

by James Perkins (Jira)

James Perkins created WFCORE-4518: ------------------------------------- Summary: Ensure the ServiceTarget is stable for the subsystem test KernelServices Key: WFCORE-4518 URL: https://issues.jboss.org/browse/WFCORE-4518 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: James Perkins Assignee: James Perkins There is potential that an operation is executed for a runtime resource in the subsystem tests if the {{ServiceTarget}} is not yet stable. Using a {{StabilityMonitor}} should fix this issue. Example stack trace when a test fails {code} org.jboss.as.controller.OperationFailedException: undefined [ undefined ] at org.jboss.as.model.test.ModelTestKernelServicesImpl.executeForResult(ModelTestKernelServicesImpl.java:238) at org.jboss.as.remoting.RemotingSubsystemTestCase.testEndpointConfigurationViaSubsystemRoot(RemotingSubsystemTestCase.java:258) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12183) WildFly "spring-greeter" quickstart contains errors after import into Red Hat CodeReady Studio (missing servlet-api-3.1.jar dependency in the pom.xml)

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12183?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12183: ----------------------------------------- [~jeffmaury] Should this go in https://issues.jboss.org/projects/JBDS ? [~zcervink] This doesn't look like a WFLY issue, as the dev studio tooling is not part of WildFly. > WildFly "spring-greeter" quickstart contains errors after import into Red Hat CodeReady Studio (missing servlet-api-3.1.jar dependency in the pom.xml) > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-12183 > URL: https://issues.jboss.org/browse/WFLY-12183 > Project: WildFly > Issue Type: Bug > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Brian Stansberry > Priority: Major > Attachments: error_msg.png > > > *Issue solved by extending the pom.xml by adding the following dependency:* > <dependency> > <groupId>javax.servlet</groupId> > <artifactId>javax.servlet-api</artifactId> > <version>3.1.0</version> > <scope>provided</scope> > </dependency> > *SOURCE: StackOverflow:* > https://stackoverflow.com/questions/22756153/the-superclass-javax-servlet... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4138) Building a KJAR using Decision Table Templates throws NPE

by Gary Hu (Jira)

[ https://issues.jboss.org/browse/DROOLS-4138?page=com.atlassian.jira.plugi... ] Gary Hu closed DROOLS-4138. --------------------------- > Building a KJAR using Decision Table Templates throws NPE > --------------------------------------------------------- > > Key: DROOLS-4138 > URL: https://issues.jboss.org/browse/DROOLS-4138 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final, 7.23.0.Final > Reporter: Carl Mes > Assignee: Mario Fusco > Priority: Critical > Attachments: DecisionTableConfigurationImpl.java > > > Steps to building a new KJar by defining Resource objects and adding then using KieFileSystem.write(), if a Decision Table Template resource type is added then we get a null pointer exception when the KieBuilder.buildAll() method is invoked. > Sample code that demonstrates this error can be found here: https://github.com/carlmes/decision-table-template, specifically the notes in [TestDecisionTableBuild.java|https://github.com/carlmes/decision-table-tem...]. > Red Hat support case: https://access.redhat.com/support/cases/#/case/02397413 > I have created a proposed fix in [DecisionTableConfigurationImpl.java|https://github.com/kiegroup/drools/bl...], by implementing the missing properties in the fromProperties and toProperties methods. Please see attached updated file that has been tested to fix the issue locally. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4501) Provide XML schema for credential-reference

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4501?page=com.atlassian.jira.plugi... ] Farah Juma reassigned WFCORE-4501: ---------------------------------- Assignee: Farah Juma > Provide XML schema for credential-reference > ------------------------------------------- > > Key: WFCORE-4501 > URL: https://issues.jboss.org/browse/WFCORE-4501 > Project: WildFly Core > Issue Type: Enhancement > Components: Management, Security > Reporter: Jeff Mesnil > Assignee: Farah Juma > Priority: Major > Labels: credential-reference, eap72 > Fix For: 10.0.0.Beta1 > > > With https://issues.jboss.org/browse/EAP7-538, all passwords references in the subsystems must support credential references. > The model attribute is provided by wildlfy-controller module (including its XML parser and marshaller) but the corresponding XML element has been added directly to the subsystems XML schemas. This will become a maintenance issue when/if the credential references has to be updated and all the subsystems schema risk to be out of sync with the actual code reading/writing the credential reference. > We should follow the same design than for threads attributes (provided by the willdfly-threads module): the wildlfy-controller module provides a XML schema for the credential-references with its own versioned namespace and any subsystem that requires it will just refer to it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4161: --------------------------------------- [~tari_manga] FYI > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4162) Scenario Test: UX for background data

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4162: ------------------------------------- Summary: Scenario Test: UX for background data Key: DROOLS-4162 URL: https://issues.jboss.org/browse/DROOLS-4162 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Tao Zhu As user I want to be able to specify a set of data shared by all the scenarios inside a simulation. All the data will be not editable. Please refer to Cucumber background feature for details https://cucumber.io/docs/gherkin/reference/#background -- 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