[JBoss JIRA] (DROOLS-3110) [DMN Designer] Unable to deploy model with custom data type
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3110?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3110:
-------------------------------------
Hi All, I created [^a_dmn.dmn] using [PR|https://github.com/kiegroup/kie-wb-common/pull/2210], fixed manually node name, but still see this errors:
{code}
12:06:54,004 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 7) Unable to resolve type reference '{https://github.com/kiegroup/drools/kie-dmn}tLength' on node 'tVacation'
12:06:54,005 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 7) Unable to resolve type reference 'tVacation' on node 'iData'
{code}
> [DMN Designer] Unable to deploy model with custom data type
> -----------------------------------------------------------
>
> Key: DROOLS-3110
> URL: https://issues.jboss.org/browse/DROOLS-3110
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Blocker
> Labels: drools-tools
> Attachments: a1.dmn, a2.dmn, a_dmn.dmn, error.log
>
>
> I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log.
> h2. Another steps to reproduce
> Run the code snippet below
> {code:java}
> final DMNRuntime runtime = DMNRuntimeUtil.createRuntime("a2.dmn", this.getClass() );
> final DMNModel dmnModel = runtime.getModel("https://github.com/kiegroup/drools/kie-dmn", "a2" );
> assertThat( DMNRuntimeUtil.formatMessages( dmnModel.getMessages() ), dmnModel.hasErrors(), is( false ) );
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3038) [DMN Designer] Added type can not be resolved
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3038?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3038:
--------------------------------
Attachment: a_dmn.dmn
> [DMN Designer] Added type can not be resolved
> ---------------------------------------------
>
> Key: DROOLS-3038
> URL: https://issues.jboss.org/browse/DROOLS-3038
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Blocker
> Labels: drools-tools
> Attachments: DROOLS-3038.dmn, Screenshot from 2018-09-26 12-57-20.png, Screenshot from 2018-09-26 12-58-02.png, Screenshot from 2018-09-26 12-58-12.png, a_dmn.dmn
>
>
> {{12:53:34,884 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 3) Unable to resolve type reference 'tNum' on node 'Decision-1'}} is error shown to user after reopening DMN model with used new defined item definition.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3038) [DMN Designer] Added type can not be resolved
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3038?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3038:
-------------------------------------
Hi All, I created [^a_dmn.dmn] using [PR|https://github.com/kiegroup/kie-wb-common/pull/2210], fixed manually node name, but still see this errors:
{code}
12:06:54,004 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 7) Unable to resolve type reference '{https://github.com/kiegroup/drools/kie-dmn}tLength' on node 'tVacation'
12:06:54,005 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 7) Unable to resolve type reference 'tVacation' on node 'iData'
{code}
> [DMN Designer] Added type can not be resolved
> ---------------------------------------------
>
> Key: DROOLS-3038
> URL: https://issues.jboss.org/browse/DROOLS-3038
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Blocker
> Labels: drools-tools
> Attachments: DROOLS-3038.dmn, Screenshot from 2018-09-26 12-57-20.png, Screenshot from 2018-09-26 12-58-02.png, Screenshot from 2018-09-26 12-58-12.png, a_dmn.dmn
>
>
> {{12:53:34,884 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 3) Unable to resolve type reference 'tNum' on node 'Decision-1'}} is error shown to user after reopening DMN model with used new defined item definition.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3110) [DMN Designer] Unable to deploy model with custom data type
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3110?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3110:
--------------------------------
Attachment: a_dmn.dmn
> [DMN Designer] Unable to deploy model with custom data type
> -----------------------------------------------------------
>
> Key: DROOLS-3110
> URL: https://issues.jboss.org/browse/DROOLS-3110
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Blocker
> Labels: drools-tools
> Attachments: a1.dmn, a2.dmn, a_dmn.dmn, error.log
>
>
> I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log.
> h2. Another steps to reproduce
> Run the code snippet below
> {code:java}
> final DMNRuntime runtime = DMNRuntimeUtil.createRuntime("a2.dmn", this.getClass() );
> final DMNModel dmnModel = runtime.getModel("https://github.com/kiegroup/drools/kie-dmn", "a2" );
> assertThat( DMNRuntimeUtil.formatMessages( dmnModel.getMessages() ), dmnModel.hasErrors(), is( false ) );
> {code}
--
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 resolved DROOLS-3182.
-----------------------------------
Fix Version/s: 7.14.0.Final
Resolution: Done
Resolving this. Fixed by commit mentioned in my previous comment.
> 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
> Fix For: 7.14.0.Final
>
>
> {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
[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:
---------------------------------------
After investigation, this error is expected. The issue is based on trying to run 7.13.0.Final on EAP 7.2, which contains newer jackson artifacts, so it causes a dependency version conflict. There was alignment with the jackson version done in the commit I mentioned previously [1], so that should be available in 7.14.0.Final.
[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
[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 edited comment on DROOLS-2569 at 10/30/18 5:25 AM:
---------------------------------------------------------------
[~tari_manga] Hi, it is resolved for most combinations of connected nodes, however magnet points are not marshalled for connections that has either source or target node Text Annotation.
Before save:
!before_save.png|thumbnail!
After save:
!after_save.png|thumbnail!
was (Author: jomarko):
[~tari_manga] Hi, it is resolved for most combinations of connected nodes, however magnet points are not marshalled for connections that has either source or target node Text 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
> Attachments: after_save.png, before_save.png
>
>
> 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