[JBoss JIRA] (DROOLS-2880) Show all top level custom Data Types in the dialog, instead of only the selected one
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2880?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2880:
--------------------------------
Description:
Show all top level custom Data Types in the dialog, instead of only the selected one. Even when the user does not have any ItemDefinition, the dialog must lunch.
h3. Acceptance test
- No definitions present (/)
- Invalid definition present
- More than 20 definitions present (/)
-- Able to scroll
-- !Screenshot from 2018-08-31 15-42-20.png|thumbnail!
was:
Show all top level custom Data Types in the dialog, instead of only the selected one. Even when the user does not have any ItemDefinition, the dialog must lunch.
h3. Acceptance test
- No definitions present (/)
- Invalid definition present
- More than 20 definitions present (/)
-- Able to scroll
--
> Show all top level custom Data Types in the dialog, instead of only the selected one
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-2880
> URL: https://issues.jboss.org/browse/DROOLS-2880
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: Screenshot from 2018-08-31 15-42-20.png
>
>
> Show all top level custom Data Types in the dialog, instead of only the selected one. Even when the user does not have any ItemDefinition, the dialog must lunch.
> h3. Acceptance test
> - No definitions present (/)
> - Invalid definition present
> - More than 20 definitions present (/)
> -- Able to scroll
> -- !Screenshot from 2018-08-31 15-42-20.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (DROOLS-2880) Show all top level custom Data Types in the dialog, instead of only the selected one
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2880?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2880:
--------------------------------
Description:
Show all top level custom Data Types in the dialog, instead of only the selected one. Even when the user does not have any ItemDefinition, the dialog must lunch.
h3. Acceptance test
- No definitions present (/)
- Invalid definition present
- More than 20 definitions present (/)
-- Able to scroll
was:
Show all top level custom Data Types in the dialog, instead of only the selected one. Even when the user does not have any ItemDefinition, the dialog must lunch.
h3. Acceptance test
- No definitions present
- Invalid definition present
- Unsupported definition present
- More than 20 definitions present
> Show all top level custom Data Types in the dialog, instead of only the selected one
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-2880
> URL: https://issues.jboss.org/browse/DROOLS-2880
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> Show all top level custom Data Types in the dialog, instead of only the selected one. Even when the user does not have any ItemDefinition, the dialog must lunch.
> h3. Acceptance test
> - No definitions present (/)
> - Invalid definition present
> - More than 20 definitions present (/)
> -- Able to scroll
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (DROOLS-2716) [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2716?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2716:
--------------------------------
Description:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel (?)
-- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
- Build and deploy after structure change
-- BAQE-589
was:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel (?)
-- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
- Build and deploy after structure change
-- BAQE-589
- Loading (x)
--
> [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2716
> URL: https://issues.jboss.org/browse/DROOLS-2716
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> - When the user changes a row in the "Field name" column, the DMN model needs to be updated;
> - When the user changes a row in the "Field type" column, the DMN model needs to be updated.
> h3. Aceeptance test
> Changed data structure
> - After save and reopen (x)
> -- Change to structure is not propagated DROOLS-2947
> - Change of structure is propagated to other model elements (/)
> - Change of structure is propagated to properties panel (x)
> -- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
> - Change of structure is propagated into the dialog (x)
> -- DROOLS-2949
> - Edit multiple items in parallel (?)
> -- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
> - Build and deploy after structure change
> -- BAQE-589
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (DROOLS-2716) [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2716?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2716:
--------------------------------
Description:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel (?)
-- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
- Build and deploy after structure change
-- BAQE-589
- Loading (x)
--
was:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel (?)
-- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
- Build and deploy after structure change
-- BAQE-589
> [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2716
> URL: https://issues.jboss.org/browse/DROOLS-2716
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> - When the user changes a row in the "Field name" column, the DMN model needs to be updated;
> - When the user changes a row in the "Field type" column, the DMN model needs to be updated.
> h3. Aceeptance test
> Changed data structure
> - After save and reopen (x)
> -- Change to structure is not propagated DROOLS-2947
> - Change of structure is propagated to other model elements (/)
> - Change of structure is propagated to properties panel (x)
> -- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
> - Change of structure is propagated into the dialog (x)
> -- DROOLS-2949
> - Edit multiple items in parallel (?)
> -- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
> - Build and deploy after structure change
> -- BAQE-589
> - Loading (x)
> --
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (DROOLS-2716) [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2716?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2716:
--------------------------------
Description:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel (?)
-- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
- Build and deploy after structure change
-- BAQE-589
was:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel (?)
-- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
- Build and deploy after structure change
> [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2716
> URL: https://issues.jboss.org/browse/DROOLS-2716
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> - When the user changes a row in the "Field name" column, the DMN model needs to be updated;
> - When the user changes a row in the "Field type" column, the DMN model needs to be updated.
> h3. Aceeptance test
> Changed data structure
> - After save and reopen (x)
> -- Change to structure is not propagated DROOLS-2947
> - Change of structure is propagated to other model elements (/)
> - Change of structure is propagated to properties panel (x)
> -- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
> - Change of structure is propagated into the dialog (x)
> -- DROOLS-2949
> - Edit multiple items in parallel (?)
> -- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
> - Build and deploy after structure change
> -- BAQE-589
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-10621) Server stop indefinitely blocked by DistributableSessionManager in lifecycleLock.writeLockInterruptibly()
by Petr H (JIRA)
[ https://issues.jboss.org/browse/WFLY-10621?page=com.atlassian.jira.plugin... ]
Petr H commented on WFLY-10621:
-------------------------------
Finally was able to switch the environment to the WildFly 14 (Final) so will test it (it may take some time to reproduce this issue).
> Server stop indefinitely blocked by DistributableSessionManager in lifecycleLock.writeLockInterruptibly()
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10621
> URL: https://issues.jboss.org/browse/WFLY-10621
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Final
> Environment: CentOS 7.4.1708
> Java 1.8.0_172-b11
> WildFly 11.0.0.Final
> Reporter: Petr H
> Assignee: Paul Ferraro
> Labels: clustering, sessions
> Fix For: 14.0.0.Beta2
>
> Attachments: threaddump-wfly11-stop-blocked.txt, threaddump-wfly13-stop-blocked.txt
>
>
> Note: This is report for the issue reported here first https://developer.jboss.org/thread/277883
> It can be seen at WildFly 11 and EAP 7.1 at least, however as the particular code in the DistributableSessionManager class seems to be unchanged even in WildFly 13 it's likely to occur there as well. (We test WildFly 11 because it's closest to the EAP 7.1 which is being considered for the production use later in this project)
> Stop server operation may hang indefinitely due to the thread such as the following one being blocked:
> {noformat}
> "ServerService Thread Pool -- 24" #49 prio=5 os_prio=0 tid=0x00000000035d1000 nid=0x4de1 waiting on condition [0x00007f4bddc46000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000000c4e61998> (a java.util.concurrent.locks.StampedLock)
> at java.util.concurrent.locks.StampedLock.acquireWrite(StampedLock.java:1119)
> at java.util.concurrent.locks.StampedLock.writeLockInterruptibly(StampedLock.java:413)
> at org.wildfly.clustering.web.undertow.session.DistributableSessionManager.stop(DistributableSessionManager.java:90)
> - locked <0x00000000c4e60090> (a org.wildfly.clustering.web.undertow.session.DistributableSessionManager)
> at io.undertow.servlet.core.DeploymentManagerImpl$3.call(DeploymentManagerImpl.java:599)
> at io.undertow.servlet.core.DeploymentManagerImpl$3.call(DeploymentManagerImpl.java:589)
> 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.security.SecurityContextThreadSetupAction$$Lambda$1005/749195997.call(Unknown Source)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction$$Lambda$1006/1165195653.call(Unknown Source)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction$$Lambda$1006/1165195653.call(Unknown Source)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction$$Lambda$1006/1165195653.call(Unknown Source)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction$$Lambda$1006/1165195653.call(Unknown Source)
> at io.undertow.servlet.core.DeploymentManagerImpl.stop(DeploymentManagerImpl.java:603)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:139)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$2.run(UndertowDeploymentService.java:120)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
> The related code in the DistributableSessionManager makes use of the [java.util.concurrent.locks.StampedLock.writeLockInterruptibly()|https://d...] method which can theoretically block indefinitely and thus prevent the server stop from ever completing.
> The change was introduced in the following commit [WFLY-7695 Block session manager stop until all sessions are closed|https://github.com/wildfly/wildfly/commit/94863deeb96c4536ec5e8266...]
> This can occur even in non-clustered environments (non-HA profile) with web applications just being marked as distributable (web.xml).
> We don't know what prevents the lock from being obtained (unable to determine from the thread dump) so we can't unfortunately do much about it at the moment from the application side.
> We only tried to change the infinispan web local-cache configuration due to _ISPN000136_ errors intermittedly occurring, but that seems to have no effect. We tried various combinations of *locking isolation* (REPEATABLE_READ, READ_COMMITED), *transaction locking* (OPTIMISTIC, PESSIMISTIC) and *transaction mode* (NONE, BATCH) settings and it seems to occur with all of them.
> Note: The issue doesn't occur always, only in some cases.
--
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 Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2949?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2949:
-------------------------------------
[~uxdlc] Hi. [~karreiro] implemented your proposals, however during review I realized that it is really easy to achieve inconssitent state if we allow eidtor of multiple custom data types in parallel. Would be disabling parallel editing in conflict with your proposals?
> [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
[JBoss JIRA] (DROOLS-2716) [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2716?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2716:
--------------------------------
Description:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel (?)
-- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
- Build and deploy after structure change
was:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel
-- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
- Build and deploy after structure change
> [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2716
> URL: https://issues.jboss.org/browse/DROOLS-2716
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> - When the user changes a row in the "Field name" column, the DMN model needs to be updated;
> - When the user changes a row in the "Field type" column, the DMN model needs to be updated.
> h3. Aceeptance test
> Changed data structure
> - After save and reopen (x)
> -- Change to structure is not propagated DROOLS-2947
> - Change of structure is propagated to other model elements (/)
> - Change of structure is propagated to properties panel (x)
> -- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
> - Change of structure is propagated into the dialog (x)
> -- DROOLS-2949
> - Edit multiple items in parallel (?)
> -- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
> - Build and deploy after structure change
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (DROOLS-2716) [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2716?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2716:
--------------------------------
Description:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel
-- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
- Build and deploy after structure change
was:
- When the user changes a row in the "Field name" column, the DMN model needs to be updated;
- When the user changes a row in the "Field type" column, the DMN model needs to be updated.
h3. Aceeptance test
Changed data structure
- After save and reopen (x)
-- Change to structure is not propagated DROOLS-2947
- Change of structure is propagated to other model elements (/)
- Change of structure is propagated to properties panel (x)
-- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
- Change of structure is propagated into the dialog (x)
-- DROOLS-2949
- Edit multiple items in parallel
- Build and deploy after structure change
> [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2716
> URL: https://issues.jboss.org/browse/DROOLS-2716
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> - When the user changes a row in the "Field name" column, the DMN model needs to be updated;
> - When the user changes a row in the "Field type" column, the DMN model needs to be updated.
> h3. Aceeptance test
> Changed data structure
> - After save and reopen (x)
> -- Change to structure is not propagated DROOLS-2947
> - Change of structure is propagated to other model elements (/)
> - Change of structure is propagated to properties panel (x)
> -- Properties panel has to be reopened, or element reselected or similar workaround DROOLS-2948
> - Change of structure is propagated into the dialog (x)
> -- DROOLS-2949
> - Edit multiple items in parallel
> -- I think this should be disabled as it is really easy then to achieve inconsistent state see DROOLS-2949
> - Build and deploy after structure change
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-10961) MP-OpenTracing Jaeger's can't see a concrete sender
by Juraci Paixão Kröhling (JIRA)
[ https://issues.jboss.org/browse/WFLY-10961?page=com.atlassian.jira.plugin... ]
Juraci Paixão Kröhling updated WFLY-10961:
------------------------------------------
Description: One of the last changes made to WF 14 was to split the MP-OpenTracing dependencies into smaller modules. This introduced a bug where the Jaeger Core module can't see a Sender from Jaeger Thrift. This is loaded via the Service Loader, so, Jaeger Core has to be shipped with Jaeger Thrift on the same module, to avoid a circular dependency (as Jaeger Thrift depends on classes defined on Jaeger Core). (was: One of the last changes made to WF 14 was to split the dependencies into smaller modules. This introduced a bug where the Jaeger Core module can't see a Sender from Jaeger Thrift. This is loaded via the Service Loader, so, Jaeger Core has to be shipped with Jaeger Thrift on the same module, to avoid a circular dependency (as Jaeger Thrift depends on classes defined on Jaeger Core).)
> MP-OpenTracing Jaeger's can't see a concrete sender
> ---------------------------------------------------
>
> Key: WFLY-10961
> URL: https://issues.jboss.org/browse/WFLY-10961
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 14.0.0.Final
> Reporter: Juraci Paixão Kröhling
> Assignee: Juraci Paixão Kröhling
>
> One of the last changes made to WF 14 was to split the MP-OpenTracing dependencies into smaller modules. This introduced a bug where the Jaeger Core module can't see a Sender from Jaeger Thrift. This is loaded via the Service Loader, so, Jaeger Core has to be shipped with Jaeger Thrift on the same module, to avoid a circular dependency (as Jaeger Thrift depends on classes defined on Jaeger Core).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months