[JBoss JIRA] (DROOLS-3199) [DMN Designer] Clear properties panel when multiple cells are selected
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3199?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3199:
-----------------------------------
Story Points: 3
> [DMN Designer] Clear properties panel when multiple cells are selected
> ----------------------------------------------------------------------
>
> Key: DROOLS-3199
> URL: https://issues.jboss.org/browse/DROOLS-3199
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
>
> The user of the DMN Designer has possibility to set properties of expression grid table cell via properties panel. The problem occurs if multiple cells are selected. Then properties panel shows properties bound to last selected cell what is not desired. Properties panel should be empty if multiple cells are selected.
> h2. Manual acceptance test
> Properties panel is empty if multiple cells (including headers) are selected
> - Decision Table
> - Function
> - Context
> - Invocation
> - Relation
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3199) [DMN Designer] Clear properties panel when multiple cells are selected
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3199?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3199:
-----------------------------------
Sprint: 2018 Week 42-44
> [DMN Designer] Clear properties panel when multiple cells are selected
> ----------------------------------------------------------------------
>
> Key: DROOLS-3199
> URL: https://issues.jboss.org/browse/DROOLS-3199
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
>
> The user of the DMN Designer has possibility to set properties of expression grid table cell via properties panel. The problem occurs if multiple cells are selected. Then properties panel shows properties bound to last selected cell what is not desired. Properties panel should be empty if multiple cells are selected.
> h2. Manual acceptance test
> Properties panel is empty if multiple cells (including headers) are selected
> - Decision Table
> - Function
> - Context
> - Invocation
> - Relation
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-2569) [DMN Designer] Marshalling of magnet positions
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2569?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2569:
--------------------------------
Description:
When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
[~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
h2. PR Acceptance test
In DMN Designer, change magnet position in:
- Source node
-- BKM, BKS, Decision, Input
- Target node
-- BKM, BKS, Decision (/), Annotation (x)
was:
When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
[~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
h2. PR Acceptance test
In DMN Designer, change magnet position in:
- Source node
-- BKM, BKS, Decision, Input
- Target node
-- BKM, BKS, Decision, Annotation (x)
> [DMN Designer] Marshalling of magnet positions
> ----------------------------------------------
>
> Key: DROOLS-2569
> URL: https://issues.jboss.org/browse/DROOLS-2569
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Matteo Mortari
> Priority: Major
> Labels: drools-tools
>
> When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
> [~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
> h2. PR Acceptance test
> In DMN Designer, change magnet position in:
> - Source node
> -- BKM, BKS, Decision, Input
> - Target node
> -- BKM, BKS, Decision (/), Annotation (x)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-2569) [DMN Designer] Marshalling of magnet positions
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2569?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2569:
--------------------------------
Description:
When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
[~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
h2. PR Acceptance test
In DMN Designer, change magnet position in:
- Source node
-- BKM, BKS, Decision, Input
- Target node
-- BKM, BKS, Decision, Annotation (x)
was:
When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
[~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
h2. PR Acceptance test
In DMN Designer, change magnet position in:
- Source node
-- BKM, BKS, Decision, Input
- Target node
-- BKM, BKS, Decision, Annotation
> [DMN Designer] Marshalling of magnet positions
> ----------------------------------------------
>
> Key: DROOLS-2569
> URL: https://issues.jboss.org/browse/DROOLS-2569
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Matteo Mortari
> Priority: Major
> Labels: drools-tools
>
> When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
> [~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
> h2. PR Acceptance test
> In DMN Designer, change magnet position in:
> - Source node
> -- BKM, BKS, Decision, Input
> - Target node
> -- BKM, BKS, Decision, Annotation (x)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3205) [DMN Designer][IE11] Missing Structure option
by Jozef Marko (Jira)
Jozef Marko created DROOLS-3205:
-----------------------------------
Summary: [DMN Designer][IE11] Missing Structure option
Key: DROOLS-3205
URL: https://issues.jboss.org/browse/DROOLS-3205
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.14.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Attachments: Screenshot from 2018-10-30 09-09-52.png
The *manage custom data type* dialog misses the *Structure* option for the IE11, see the attached screenshot. Other browsers works fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Klara Kufova commented on DROOLS-3193:
--------------------------------------
[~uxdlc], I don't know if it helps, but from my experience:
* yes, when I'm absolutely sure what scenarios I want to create, I always prepare the table first and then I'm populating the table with column types;
* yes, if there are only small changes to do, it's always quicker to duplicate;
* yes, I think so. I am not sure what exactly you mean, but I think adding additional instances of the same object is a frequent procedure.
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4189) Hard coded failIfNoTests=true fail WF core build if no tests are executed
by Miroslav Novak (Jira)
Miroslav Novak created WFCORE-4189:
--------------------------------------
Summary: Hard coded failIfNoTests=true fail WF core build if no tests are executed
Key: WFCORE-4189
URL: https://issues.jboss.org/browse/WFCORE-4189
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Reporter: Miroslav Novak
Assignee: Miroslav Novak
There is hard coded <failIfNoTests>true</failIfNoTests> in maven surefire plugin in testsuite/rbac/pom.xml which causes that running this module fails even if -DfailIfNoTests=false in maven command.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3182) Kie server on eap72 java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with
by Tibor Zimányi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3182?page=com.atlassian.jira.plugi... ]
Tibor Zimányi commented on DROOLS-3182:
---------------------------------------
I am afraid this could be caused by cancelling jackson artifacts version override in kie-parent. See here [1]. I will test the older versions we used and let you know.
[1] https://github.com/kiegroup/droolsjbpm-build-bootstrap/commit/4bce1ca71db...
> Kie server on eap72 java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with
> --------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3182
> URL: https://issues.jboss.org/browse/DROOLS-3182
> Project: Drools
> Issue Type: Bug
> Components: Cloud, kie server
> Affects Versions: 7.13.0.Final
> Reporter: Filippe Spolti
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
>
> {code:java}
> 16:59:13,571 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service jboss.deployment.unit."ROOT.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.unit."ROOT.war".undertow-deployment: java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with(Lcom/fasterxml/jackson/databind/AnnotationIntrospector;)Lcom/fasterxml/jackson/databind/SerializationConfig;
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with(Lcom/fasterxml/jackson/databind/AnnotationIntrospector;)Lcom/fasterxml/jackson/databind/SerializationConfig;
> at org.kie.server.api.marshalling.json.JSONMarshaller.configureMarshaller(JSONMarshaller.java:155)
> at org.kie.server.api.marshalling.json.JSONMarshaller.<init>(JSONMarshaller.java:128)
> at org.kie.server.api.marshalling.BaseMarshallerBuilder.build(BaseMarshallerBuilder.java:43)
> at org.kie.server.api.marshalling.MarshallerFactory.getMarshaller(MarshallerFactory.java:52)
> at org.kie.server.api.marshalling.MarshallerFactory.getMarshaller(MarshallerFactory.java:41)
> at org.kie.server.services.jbpm.JbpmKieServerExtension.registerDefaultQueryDefinitions(JbpmKieServerExtension.java:760)
> at org.kie.server.services.jbpm.JbpmKieServerExtension.init(JbpmKieServerExtension.java:198)
> at org.kie.server.services.impl.KieServerImpl.init(KieServerImpl.java:126)
> at org.kie.server.services.impl.KieServerLocator.<clinit>(KieServerLocator.java:23)
> at org.kie.server.services.Bootstrap.contextInitialized(Bootstrap.java:51)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
> ... 8 more
> 16:59:13,586 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ROOT.war\".undertow-deployment" => "java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with(Lcom/fasterxml/jackson/databind/AnnotationIntrospector;)Lcom/fasterxml/jackson/databind/SerializationConfig;
> Caused by: java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with(Lcom/fasterxml/jackson/databind/AnnotationIntrospector;)Lcom/fasterxml/jackson/databind/SerializationConfig;"}}
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month