[JBoss JIRA] (DROOLS-2945) DMN Designer - opening data type dialog shows warning in browser console
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2945?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2945:
---------------------------------------
Sprint: 2018 Week 36-38
> DMN Designer - opening data type dialog shows warning in browser console
> ------------------------------------------------------------------------
>
> Key: DROOLS-2945
> URL: https://issues.jboss.org/browse/DROOLS-2945
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
> Attachments: Port Clearance Rules - Solution 3.dmn
>
>
> Opening *manage custom data types dialog* shows warning in the browser console.
> {code}
> org.kie.workbench.drools.KIEDroolsWebapp-0.js:22170 13:54:49 WARNING [TemplateUtil] Replacing Element type [SPAN] in org/kie/workbench/common/dmn/client/editors/types/listview/DataTypeListItemView.html with type [TD] for type in org.kie.workbench.common.dmn.client.editors.types.listview.DataTypeListItemView
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFCORE-2066) Kill and destroy operations on the server-group
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2066?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2066:
------------------------------------------
[~ahoffer] Re: the difference between 'kill' and 'destroy' here's a good summary from [~claudio4j] that I saw:
{quote}
About the difference between kill and destroy:
Short answer: "destroy" calls the internal syscall "kill -9" from native JDK. "kill" calls the command line "kill -9", if it is not available, it internally calls the previous "destroy".
If the user just wants to forcibly terminates the process, use "kill"
kill: If there is a "kill" command on the OS (unix has "kill", windows has "taskkill"), this command will be called to forcibly kill the process with kill -9 (SIGKILL on linux) and /f (windows). If the "kill" command is not available on the OS, then the "destroy" is called on the process.
destroy: JDK provides an implementation to forcibly destroy the process, it will vary on each OS, on linux it call "kill" kernel api (the same as the above kill command) with SIGKILL signal, this is the same as calling the kill -9.
{quote}
I mildly regret that we have both 'kill' and 'destroy' as the distinction is quite esoteric. It's one of those things from back in the early history of AS 7 that still lives on for compatibility reasons.
> Kill and destroy operations on the server-group
> -----------------------------------------------
>
> Key: WFCORE-2066
> URL: https://issues.jboss.org/browse/WFCORE-2066
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Management
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Labels: domain-mode
> Fix For: 4.0.0.Alpha3
>
>
> The server-config resources expose kill and destroy operations; it would be useful to have these on the server-group as well. If some problem (e.g. a bad deployment) is causing all servers in the group to hang it is nice to be able to kill/destroy them in one op versus having to identify all members and kill them individually.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (DROOLS-2949) [DMN Designer] Change of data type is not propagated to manage dialog
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2949?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-2949 at 8/31/18 1:00 PM:
---------------------------------------------------------------------
[~jomarko] This is a known issue.
We had some discussions about this on Slack and we decided that propagating the changes would be the best approach. However, when I estimated/planned the DROOLS-2716, I was not considering the propagation work, so I created the DROOLS-2762 to address this scenario.
In summary, I think the https://issues.jboss.org/browse/DROOLS-2762 will solve the propagation bug :) and the DROOLS-2949 is a duplicated JIRA.
was (Author: karreiro):
[~jomarko] This is a known issue. The https://issues.jboss.org/browse/DROOLS-2762 will solve the propagation bug :)
> [DMN Designer] Change of data type is not propagated to manage dialog
> ---------------------------------------------------------------------
>
> Key: DROOLS-2949
> URL: https://issues.jboss.org/browse/DROOLS-2949
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: Screenshot from 2018-08-31 14-59-52.png, itemDef-dependency.dmn
>
>
> User is able to achieve inconsistent state in *Manage custom data type dialog* See the attached picture. There is changed top level itemDefinition *Address* to *Adress111* however the itemDefinition *Person* stil shows it address field as *Adress*, it should be *Adress111* too.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months