[JBoss JIRA] (DROOLS-3184) [DMN Designer] Edge source and target WayPoints are same
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3184?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3184:
----------------------------------------
Bit more information.
When the {{MagnetConnector}} is created from the toolbox it is connected to the right side of the source shape and left side of the target shape. Whereas when the connector is created _manually_ by clicking on the connector icon in the toolbox and dragging to a target shape the {{MagnetConnection}} is set to connect to the middle/centre of the shapes.
The {{MagnetConnection}} has a property to ascertain if it is connected to the middle/left or right however it is [marked|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-commo...] as transient and hence gets thrown away when marshalled to the server for marshalling to DMN XML. So we cannot rely on this field :-(
We need to stick with:
- If the "connection source/target location is {{null}}" assume it's the centre of the shape.
- If it is non-{{null}} it is relative to the source/target shape location.
> [DMN Designer] Edge source and target WayPoints are same
> --------------------------------------------------------
>
> Key: DROOLS-3184
> URL: https://issues.jboss.org/browse/DROOLS-3184
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-25 12-12-20.png, a1.dmn, image (2).png
>
>
> The source of DMN model has same waypoint for edge source and target. If you open the attached [^a1.dmn] model, there will be:
> {code:xml}
> <dmndi:DMNEdge id="dmnedge-_594C4BE1-52D0-4009-9D4F-9960957539FB" dmnElementRef="_594C4BE1-52D0-4009-9D4F-9960957539FB">
> <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/>
> <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/>
> </dmndi:DMNEdge>
> {code}
> However in our designer the edge has different waypoints:
> !Screenshot from 2018-10-25 12-12-20.png|thumbnail!
> In the external modeling tools, the edge is rendered according to real waypoints and this the edge is not visible:
> !image (2).png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3184) [DMN Designer] Edge source and target WayPoints are same
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3184?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3184:
----------------------------------------
It looks like we need to do the following for the waypoints for connections.
- Get the {{ViewConnector}}
- Get the source {{Connection}} and target {{Connection}}
- If the {{Connection}} is an instanceof {{MagnetConnection}} the end-points are either:
-- Undefined i.e. {{null}} (IDK why, need to raise an issue with the Stunner people) If the connection was created from the Toolbox (i.e. add a InputData and then the Decision from it using the Decision toolbox icon). If the connection was created by clicking on connector icon in the toolbox it is non-null.. but keep reading!
-- Contains the {{Point2D}} *relative* to the parent shape (this is why the way-points in this JIRA are 50, 25 as this is the _centre_ of the shape they are connected to)
So for both source and target connections:-
- If it is {{null}} get the source/target shape's location and dimensions and set the DMNDI point to the centre of the shape's location (i.e. {{x + width/2}} etc).
- If it is non-{{null}} get the source/target shape's location and add the non-{{null}} connection {{Point2D}} to it. This is the DMNDI location.
> [DMN Designer] Edge source and target WayPoints are same
> --------------------------------------------------------
>
> Key: DROOLS-3184
> URL: https://issues.jboss.org/browse/DROOLS-3184
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-25 12-12-20.png, a1.dmn, image (2).png
>
>
> The source of DMN model has same waypoint for edge source and target. If you open the attached [^a1.dmn] model, there will be:
> {code:xml}
> <dmndi:DMNEdge id="dmnedge-_594C4BE1-52D0-4009-9D4F-9960957539FB" dmnElementRef="_594C4BE1-52D0-4009-9D4F-9960957539FB">
> <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/>
> <di:waypoint xmlns:di="http://www.omg.org/spec/DMN/20180521/DI/" x="50" y="25"/>
> </dmndi:DMNEdge>
> {code}
> However in our designer the edge has different waypoints:
> !Screenshot from 2018-10-25 12-12-20.png|thumbnail!
> In the external modeling tools, the edge is rendered according to real waypoints and this the edge is not visible:
> !image (2).png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3182) Kie server on eap72 java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with
by David Ward (Jira)
[ https://issues.jboss.org/browse/DROOLS-3182?page=com.atlassian.jira.plugi... ]
David Ward updated DROOLS-3182:
-------------------------------
Summary: Kie server on eap72 java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with (was: Kie server on eap72 java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig)
> 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, 8 months
[JBoss JIRA] (SECURITY-847) LdapExtLoginModule rolesSearch yields Decode Error
by Juergen H (Jira)
[ https://issues.jboss.org/browse/SECURITY-847?page=com.atlassian.jira.plug... ]
Juergen H commented on SECURITY-847:
------------------------------------
in my efforts migrating from wildfly-8.2.1.Final to wildfly-14.0.1.Final I found this not to be an issue any more with
org.jboss.security.negotiation.AdvancedLdapLoginModule in jboss-negotiation-extras-3.0.4.Final.jar
seems it got fixed somewhere in between.
close?
> LdapExtLoginModule rolesSearch yields Decode Error
> --------------------------------------------------
>
> Key: SECURITY-847
> URL: https://issues.jboss.org/browse/SECURITY-847
> Project: PicketBox
> Issue Type: Feature Request
> Components: PicketBox
> Affects Versions: PicketBox_4_0_21.Beta1
> Reporter: Juergen H
> Assignee: Peter Skopek
> Priority: Major
> Labels: ldap
>
> Migrating an application using LdapExtLoginModule from jboss-4.2.3.GA to wildfly-8.1
> Encountered a problem with ldap roles search:
> javax.naming.NamingException: [LDAP: error code 1 - Decode Error in response from BE (backend problem)]; remaining name 'ou=
> debugging and comparing result:
> jboss-4.2.3.GA LdapExtLoginModule does set javax.naming.directory.SearchControls.setReturningAttributes for role search:
> {code:title=jboss-4.2.3.GA LdapExtLoginModule}
> SearchControls constraints = new SearchControls();
> constraints.setSearchScope(searchScope);
> constraints.setReturningAttributes(new String[0]);
> constraints.setTimeLimit(searchTimeLimit);
> rolesSearch(ctx, constraints, username, userDN, recursion, 0);
> {code}
> wildfly-8.1 picketbox-4.0.21.Beta1.jar LdapExtLoginModule does NOT set javax.naming.directory.SearchControls.setReturningAttributes for role search:
> {code:title=wildfly-8.1 LdapExtLoginModule}
> // Query for roles matching the role filter
> SearchControls constraints = new SearchControls();
> constraints.setSearchScope(searchScope);
> constraints.setTimeLimit(searchTimeLimit);
> rolesSearch(ctx, constraints, username, userDN, recursion, 0);
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3186) [DMN Designer] Remove Shape and Font border properties
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3186?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3186:
--------------------------------
Description:
{quote}
Offical DMNDI (of spec DMNv1.2) has no support for Shape border size, Font border size. I will not persist this information.
{quote}
> Did you want these properties removed from the Editor?
> I would say given the current deadlines the safest approach is to temporarily hide and disable them
h2. Acceptance test
- Build and deploy on kie-server
- Save and reopen
was:
{quote}
Offical DMNDI (of spec DMNv1.2) has no support for Shape border size, Font border size. I will not persist this information.
{quote}
> Did you want these properties removed from the Editor?
> I would say given the current deadlines the safest approach is to temporarily hide and disable them
> [DMN Designer] Remove Shape and Font border properties
> ------------------------------------------------------
>
> Key: DROOLS-3186
> URL: https://issues.jboss.org/browse/DROOLS-3186
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> {quote}
> Offical DMNDI (of spec DMNv1.2) has no support for Shape border size, Font border size. I will not persist this information.
> {quote}
> > Did you want these properties removed from the Editor?
> > I would say given the current deadlines the safest approach is to temporarily hide and disable them
> h2. Acceptance test
> - Build and deploy on kie-server
> - Save and reopen
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3187) [DMN Designer] Add support for bend-points on connectors
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3187?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3187:
--------------------------------
Description:
DMN1.1 did not contain layout information.
DMN1.2 contains layout information and supports "bend points" in connectors.
Bend-points are supported in Stunner so should be reasonably simple to add to DMN UI.
h2. Manual acceptance test
- Save and reopen diagram where multiple bendpoints used
- Save and reopen diagram where bendpoints were removed
- Try to open externally diagram with bendpoints
- Try to deploy diagram with bendpoints on kie-server
- Firefox, Chrome, Edge
was:
DMN1.1 did not contain layout information.
DMN1.2 contains layout information and supports "bend points" in connectors.
Bend-points are supported in Stunner so should be reasonably simple to add to DMN UI.
h2. Manual acceptance test
- Save and reopen diagram where multiple bendpoints used
- Save and reopen diagram where bendpoints were removed
- Try to open externally diagram with bendpoints
- Try to deploy diagram with bendpoints on kie-server
> [DMN Designer] Add support for bend-points on connectors
> --------------------------------------------------------
>
> Key: DROOLS-3187
> URL: https://issues.jboss.org/browse/DROOLS-3187
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
>
> DMN1.1 did not contain layout information.
> DMN1.2 contains layout information and supports "bend points" in connectors.
> Bend-points are supported in Stunner so should be reasonably simple to add to DMN UI.
> h2. Manual acceptance test
> - Save and reopen diagram where multiple bendpoints used
> - Save and reopen diagram where bendpoints were removed
> - Try to open externally diagram with bendpoints
> - Try to deploy diagram with bendpoints on kie-server
> - Firefox, Chrome, Edge
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3187) [DMN Designer] Add support for bend-points on connectors
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3187?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3187:
--------------------------------
Description:
DMN1.1 did not contain layout information.
DMN1.2 contains layout information and supports "bend points" in connectors.
Bend-points are supported in Stunner so should be reasonably simple to add to DMN UI.
h2. Manual acceptance test
- Save and reopen diagram where multiple bendpoints used
- Save and reopen diagram where bendpoints were removed
- Try to open externally diagram with bendpoints
- Try to deploy diagram with bendpoints on kie-server
was:
DMN1.1 did not contain layout information.
DMN1.2 contains layout information and supports "bend points" in connectors.
Bend-points are supported in Stunner so should be reasonably simple to add to DMN UI.
> [DMN Designer] Add support for bend-points on connectors
> --------------------------------------------------------
>
> Key: DROOLS-3187
> URL: https://issues.jboss.org/browse/DROOLS-3187
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
>
> DMN1.1 did not contain layout information.
> DMN1.2 contains layout information and supports "bend points" in connectors.
> Bend-points are supported in Stunner so should be reasonably simple to add to DMN UI.
> h2. Manual acceptance test
> - Save and reopen diagram where multiple bendpoints used
> - Save and reopen diagram where bendpoints were removed
> - Try to open externally diagram with bendpoints
> - Try to deploy diagram with bendpoints on kie-server
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months