[JBoss JIRA] (DROOLS-2644) [DMN Designer] Deletion of the column causes last column width increase
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2644?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2644:
--------------------------------
Description:
There are situations when the undo of column deletion causes unexpected grid total width increase. See the steps to reproduce.
h3. Manual Accpetance Test
# Steps to reproduce fixed (/)
# Steps to reproduce fixed when decision table / relation is not top level context entry (/)
# Repeat steps to reproduce, save and reopen, edit the expression (/)
was:
There are situations when the undo of column deletion causes unexpected grid total width increase. See the steps to reproduce.
h3. Manual Accpetance Test
# Steps to reproduce fixed (/)
# Steps to reproduce fixed when decision table / relation is not top level context entry (x)
# Repeat steps to reproduce, save and reopen, edit the expression (/)
> [DMN Designer] Deletion of the column causes last column width increase
> -----------------------------------------------------------------------
>
> Key: DROOLS-2644
> URL: https://issues.jboss.org/browse/DROOLS-2644
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
>
> There are situations when the undo of column deletion causes unexpected grid total width increase. See the steps to reproduce.
> h3. Manual Accpetance Test
> # Steps to reproduce fixed (/)
> # Steps to reproduce fixed when decision table / relation is not top level context entry (/)
> # Repeat steps to reproduce, save and reopen, edit the expression (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2655:
--------------------------------
Description:
[~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
was:[~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
> [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2655
> URL: https://issues.jboss.org/browse/DROOLS-2655
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (DROOLS-2652) [DMN Designer] Different icons for different connector types
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2652?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2652:
-------------------------------------
[~manstis] [~tari_manga] Hi, this came to my mind after the meeting, could we somehow sort the icons in the context menu? I mean to have grouped nodes and connectors? Does it makes sense for you? Would it be useful from your point of view?
> [DMN Designer] Different icons for different connector types
> ------------------------------------------------------------
>
> Key: DROOLS-2652
> URL: https://issues.jboss.org/browse/DROOLS-2652
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2652 (toolbox icons).png
>
>
> The toolbox shows icons for the different connection types available from a given node.
> At the moment they are all the same icon and it is difficult to know which toolbox icon represents which connection type. Until https://issues.jboss.org/browse/DROOLS-1944 a short-term fix is to simply ensure each connection type has an icon more correctly representing its type.
> h3. Manual Acceptance test
> Each node type has appropriate connector icons in the context menu
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (DROOLS-2652) [DMN Designer] Different icons for different connector types
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2652?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2652:
--------------------------------
Description:
The toolbox shows icons for the different connection types available from a given node.
At the moment they are all the same icon and it is difficult to know which toolbox icon represents which connection type. Until https://issues.jboss.org/browse/DROOLS-1944 a short-term fix is to simply ensure each connection type has an icon more correctly representing its type.
h3. Manual Acceptance test
Each node type has appropriate connector icons in the context menu
was:
The toolbox shows icons for the different connection types available from a given node.
At the moment they are all the same icon and it is difficult to know which toolbox icon represents which connection type. Until https://issues.jboss.org/browse/DROOLS-1944 a short-term fix is to simply ensure each connection type has an icon more correctly representing its type.
> [DMN Designer] Different icons for different connector types
> ------------------------------------------------------------
>
> Key: DROOLS-2652
> URL: https://issues.jboss.org/browse/DROOLS-2652
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2652 (toolbox icons).png
>
>
> The toolbox shows icons for the different connection types available from a given node.
> At the moment they are all the same icon and it is difficult to know which toolbox icon represents which connection type. Until https://issues.jboss.org/browse/DROOLS-1944 a short-term fix is to simply ensure each connection type has an icon more correctly representing its type.
> h3. Manual Acceptance test
> Each node type has appropriate connector icons in the context menu
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months
[JBoss JIRA] (WFLY-10629) Server startup wrongly deploys all xml files and never stops
by Arnie Morein (JIRA)
[ https://issues.jboss.org/browse/WFLY-10629?page=com.atlassian.jira.plugin... ]
Arnie Morein commented on WFLY-10629:
-------------------------------------
I moved all the configuration files but standalone.xml to another folder at the same level as ./configuration. They aren't seen anymore, but again, the re-configuration never stops.
17:09:46,410 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) started in 7783ms - Started 560 of 757 services (327 services are lazy, passive or on-demand)
17:09:46,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
17:09:46,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.initial.xml" (runtime-name: "standalone.initial.xml")
17:09:46,872 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.boot.xml" (runtime-name: "standalone.boot.xml")
17:09:47,069 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
17:09:47,069 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.initial.xml" (runtime-name : "standalone.initial.xml")
17:09:47,070 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.boot.xml" (runtime-name : "standalone.boot.xml")
17:09:47,939 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory C:\dev\jboss\wildfly-13.0.0.Final\standalone
17:09:48,579 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location C:\dev\jboss\wildfly-13.0.0.Final\standalone\data\content\be\488d0bd96702306d61cd041e85f10c1f03ea37\content
17:09:48,621 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 31ms
17:09:48,627 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
17:09:48,630 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
17:09:48,631 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v1.xml" (runtime-name: "standalone.v1.xml")
17:09:48,631 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml")
17:09:48,708 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 80ms
17:09:48,711 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
17:09:48,870 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
17:09:48,870 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml")
17:09:48,871 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
17:09:48,871 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
17:09:48,871 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"
17:09:54,070 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 5ms
17:09:54,074 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
17:09:54,075 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone.v4.xml" (runtime-name: "standalone.v4.xml")
17:09:54,081 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 9ms
17:09:54,084 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
17:09:54,195 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
17:09:54,195 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v4.xml" (runtime-name : "standalone.v4.xml")
17:09:54,197 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"
> Server startup wrongly deploys all xml files and never stops
> ------------------------------------------------------------
>
> Key: WFLY-10629
> URL: https://issues.jboss.org/browse/WFLY-10629
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Reporter: Arnie Morein
> Assignee: Jason Greene
>
> I have downloaded WF 12 and 13, then imported each into Eclipse (Oxygen.3a Release (4.7.3a)), OS is Win 7/x64; then used add-user to set up admin user. Then from both the command line and from within Eclipse, when the software starts up all of the xml configuration files get deployed at the same time despite the fact that the --server-config=standalone.xml parameter is present in either environment. What's worse, it starts versioning them and re-deploying them over and over and over again.
> {quote}
> 15:45:42,229 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container
> 15:45:42,319 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
> 15:45:42,320 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-load-balancer.xml" (runtime-name : "standalone-load-balancer.xml")
> 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ha.xml" (runtime-name : "standalone-ha.xml")
> 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full.xml" (runtime-name : "standalone-full.xml")
> 15:45:42,325 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full-ha.xml" (runtime-name : "standalone-full-ha.xml")
> 15:45:42,326 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ee8.xml" (runtime-name : "standalone-ee8.xml")
> 15:45:42,407 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 15:45:42,410 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) started in 6285ms - Started 549 of 746 services (326 se
> rvices are lazy, passive or on-demand)
> 15:45:42,575 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:45:42,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone.boot.xml" (runtime-name: "standalone.boot.xml")
> 15:45:42,581 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.initial.xml" (runtime-name: "standalone.initial.xml")
> 15:45:42,724 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
> 15:45:42,725 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.initial.xml" (runtime-name : "standalone.initial.xml")
> 15:45:42,726 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.boot.xml" (runtime-name : "standalone.boot.xml")
> 15:45:47,921 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 28ms
> 15:45:47,928 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:45:47,930 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "standalone.v1.xml" (runtime-name: "standalone.v1.xml")
> 15:45:47,982 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 55ms
> 15:45:47,984 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:45:48,059 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
> 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"
> 15:45:53,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 13ms
> 15:45:53,236 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
> 15:45:53,237 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:45:53,249 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 15ms
> 15:45:53,252 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:45:53,340 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:45:53,341 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
> 15:45:53,342 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 3 months