October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3184) [DMN Designer] Edge source and target WayPoints are same

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3184?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-3184: ---------------------------------------- [~jomarko] I am indeed working on this. Without [~manstis] explaination of the Stunner behavior it would have been impossible for me to understand what's going on. > [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: Matteo Mortari > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-10-25 12-12-20.png, a1.dmn, error.log, 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3186) [DMN Designer] Remove Shape BorderSize and Font BorderSize properties

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3186?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3186: ------------------------------------- I think this is not solved properly, see master: !Screenshot from 2018-10-26 11-34-57.png|thumbnail! Compare with this PR: !Screenshot from 2018-10-26 11-36-26.png|thumbnail! There is still font border thickness > [DMN Designer] Remove Shape BorderSize and Font BorderSize 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 > Attachments: Screenshot from 2018-10-26 11-34-57.png, Screenshot from 2018-10-26 11-36-26.png > > > {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 > - No node type has these properties (x) > - Save and reopen (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3186) [DMN Designer] Remove Shape BorderSize and Font BorderSize properties

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3186?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3186: -------------------------------- Attachment: Screenshot from 2018-10-26 11-36-26.png Screenshot from 2018-10-26 11-34-57.png > [DMN Designer] Remove Shape BorderSize and Font BorderSize 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 > Attachments: Screenshot from 2018-10-26 11-34-57.png, Screenshot from 2018-10-26 11-36-26.png > > > {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 > - No node type has these properties (x) > - Save and reopen (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3186) [DMN Designer] Remove Shape BorderSize and Font BorderSize 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 - No node type has these properties (x) - 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 h2. Acceptance test - No node type has these properties - Save and reopen > [DMN Designer] Remove Shape BorderSize and Font BorderSize 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 > - No node type has these properties (x) > - Save and reopen (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11136) It is not possible to build Mojarra with JDK10+

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/WFLY-11136?page=com.atlassian.jira.plugin... ] Ingo Weiss commented on WFLY-11136: ----------------------------------- This has been fixed upstream. Is there a branch we should look at? > It is not possible to build Mojarra with JDK10+ > ----------------------------------------------- > > Key: WFLY-11136 > URL: https://issues.jboss.org/browse/WFLY-11136 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Jan Kašík > Assignee: Ingo Weiss > Priority: Major > Labels: Java11 > > It is not possible to build Mojarra with JDK10+. See [issue on project page (upstream)|https://github.com/eclipse-ee4j/mojarra/issues/4461]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2309) DNS_PING triggers warning events

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2309?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2309: --------------------------- Fix Version/s: 4.0.16 > DNS_PING triggers warning events > -------------------------------- > > Key: JGRP-2309 > URL: https://issues.jboss.org/browse/JGRP-2309 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.15 > Environment: Openshift Enterprise 3.11 > Reporter: Radim Vansa > Assignee: Sebastian Łaskawiec > Priority: Minor > Fix For: 4.0.16 > > > Using dns.DNS_PING with {{dns_query=keycloak-discovery.keycloak-test.svc.cluster.local}}, when looking into {{oc describe po my-pod-xxxxxx}} I've noticed this warning: > {code} > Warning DNSConfigForming 7m (x6 over 10m) kubelet, locksmith.lab.eng.brq.redhat.com Search Line limits were exceeded, some search paths have been omitted, the applied search line is: keycloak-test.svc.cluster.local svc.cluster.local cluster.local lab.eng.brq.redhat.com englab.eng.brq.redhat.com brq.redhat.com > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3186) [DMN Designer] Remove Shape BorderSize and Font BorderSize 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 - No node type has these properties - 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 h2. Acceptance test - Build and deploy on kie-server - Save and reopen > [DMN Designer] Remove Shape BorderSize and Font BorderSize 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 > - No node type has these properties > - Save and reopen -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3192) Change popover menus to launch on single, left mouse click.

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3192?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3192: ---------------------------------------- [~uxdlc] I'm inclined to close this JIRA as it appears to duplicate https://issues.jboss.org/browse/DROOLS-2910 > Change popover menus to launch on single, left mouse click. > ------------------------------------------------------------ > > Key: DROOLS-3192 > URL: https://issues.jboss.org/browse/DROOLS-3192 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Popover menus should launch on single, left mouse click to match PatternFly pattern: https://www.patternfly.org/pattern-library/widgets/#popover > Including: > * The decision table "decision logic" selector (menu to select logic type: Literal expression, Context, etc.) currently uses a double-left mouse click to launch the menu. Given the menu is closer in spirit (and intention) to a popover menu - to provide a more consistent and predictable user experience it would be preferable to launch this menu on a single, left mouse click. > * Decision table Data type selection popover. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3184) [DMN Designer] Edge source and target WayPoints are same

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3184?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3184: ------------------------------------- [~manstis] ok, I attached error.log just to have more info directly in jira. Next, form discussion above I am not sure if you or Matteo will solve this problem, anyway, please ping me in PR once I can have a look again. > [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: Matteo Mortari > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-10-25 12-12-20.png, a1.dmn, error.log, 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1942) [DMN Editor] InformationItem's "Name" is always the same as the containing node

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1942?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-1942: ----------------------------------- Labels: drools-tools (was: ) > [DMN Editor] InformationItem's "Name" is always the same as the containing node > ------------------------------------------------------------------------------- > > Key: DROOLS-1942 > URL: https://issues.jboss.org/browse/DROOLS-1942 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Whilst an {{InformationItem}} Node has a "Name" its value is always the same as the containing Node's "Name" (for {{InputData}}, {{Decision}} and {{BusinessKnowledgeModel}}). {{ContextEntry}}'s "Name" are not the same as outer most node's "Name" (as a {{ContextEntry}} is contained within a {{Context}} and not directly in a node itself). > It is proposed that this synchronization should be handled in the "Stunner to (org.kie) DMN model" marshalling. Therefore we need to remove the "Name" {{@FormField}} from {{InformationItem}}. > [~tari_manga] [~tirelli] Please confirm. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 October 2018