[JBoss JIRA] (DROOLS-2842) [DMN Designer] Recursive item definitions
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2842?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2842:
--------------------------------
Description:
Opening DMN model with recursive item definition inside causes unexpected error dialog with the attached error inside.
h2. Acceptance test
- Opening model with recursive item definition informs user with reasonable message and opens plain xml editor
was:Opening DMN model with recursive item definition inside causes unexpected error dialog with the attached error inside.
> [DMN Designer] Recursive item definitions
> -----------------------------------------
>
> Key: DROOLS-2842
> URL: https://issues.jboss.org/browse/DROOLS-2842
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: recursive-structure-error.log
>
>
> Opening DMN model with recursive item definition inside causes unexpected error dialog with the attached error inside.
> h2. Acceptance test
> - Opening model with recursive item definition informs user with reasonable message and opens plain xml editor
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2877) Update the top level data type, considering changes in an external/nested sub data type
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2877?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2877:
--------------------------------
Description:
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.
h2. Steps to reproduce
- Open the attached model
- Invoke manage custom data type dialog
- Change the Address item definition as shown in picture
-- Person item definition should update its fields
- Reopen the manage dialog
- Person will still have field of *Adress* type
- Click edito to this field
-- Nothing selected will be shown
-- It should select *Adress111*
h2. Acceptance test
- Steps to reproduce fixed
- Change item definition that should affect multiple item definitions
- Changing multiple item definititons in parallel is prohibited
was:
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.
h2. Steps to reproduce
- Open the attached model
- Invoke manage custom data type dialog
- Change the Address item definition as shown in picture
-- Person item definition should update its fields
- Reopen the manage dialog
- Person will still have field of *Adress* type
- Click edito to this field
-- Nothing selected will be shown
-- It should select *Adress111*
h2. Acceptance test
- Steps to reproduce fixed
- Change item definition that should affect multiple item definitions
> Update the top level data type, considering changes in an external/nested sub data type
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-2877
> URL: https://issues.jboss.org/browse/DROOLS-2877
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Guilherme Carreiro
> 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.
> h2. Steps to reproduce
> - Open the attached model
> - Invoke manage custom data type dialog
> - Change the Address item definition as shown in picture
> -- Person item definition should update its fields
> - Reopen the manage dialog
> - Person will still have field of *Adress* type
> - Click edito to this field
> -- Nothing selected will be shown
> -- It should select *Adress111*
> h2. Acceptance test
> - Steps to reproduce fixed
> - Change item definition that should affect multiple item definitions
> - Changing multiple item definititons in parallel is prohibited
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2877) Update the top level data type, considering changes in an external/nested sub data type
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2877?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2877:
--------------------------------
Description:
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.
h2. Steps to reproduce
- Open the attached model
- Invoke manage custom data type dialog
- Change the Address item definition as shown in picture
-- Person item definition should update its fields
- Reopen the manage dialog
- Person will still have field of *Adress* type
- Click edito to this field
-- Nothing selected will be shown
-- It should select *Adress111*
h2. Acceptance test
- Steps to reproduce fixed
- Change item definition that should affect multiple item definitions
was:
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.
h2. Steps to reproduce
- Open the attached model
- Invoke manage custom data type dialog
- Change the Address item definition as shown in picture
-- Person item definition should update its fields
- Reopen the manage dialog
- Person will still have field of *Adress* type
- Click edito to this field
-- Nothing selected will be shown
-- It should select *Adress111*
> Update the top level data type, considering changes in an external/nested sub data type
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-2877
> URL: https://issues.jboss.org/browse/DROOLS-2877
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Guilherme Carreiro
> 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.
> h2. Steps to reproduce
> - Open the attached model
> - Invoke manage custom data type dialog
> - Change the Address item definition as shown in picture
> -- Person item definition should update its fields
> - Reopen the manage dialog
> - Person will still have field of *Adress* type
> - Click edito to this field
> -- Nothing selected will be shown
> -- It should select *Adress111*
> h2. Acceptance test
> - Steps to reproduce fixed
> - Change item definition that should affect multiple item definitions
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10655) SEVERE error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra"
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-10655?page=com.atlassian.jira.plugin... ]
Dmitrii Tikhomirov updated WFLY-10655:
--------------------------------------
Attachment: clusterbench-ee7-bugged.ear
> SEVERE error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra"
> -------------------------------------------------------------------------------
>
> Key: WFLY-10655
> URL: https://issues.jboss.org/browse/WFLY-10655
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF
> Affects Versions: 13.0.0.Final
> Reporter: tommaso borgato
> Assignee: Dmitrii Tikhomirov
> Fix For: 14.0.0.Beta2
>
> Attachments: clusterbench-ee7-bugged.ear, clusterbench-ee7.ear
>
>
> Affected scenario is [eap-7x-failover-ejb-ejbservlet-undeploy-repl-sync|https://jenkins.hosts.m...].
> Every time the server is stated or re-started, we observed the following SEVERE logs just after clusterbench is deployed (clusterbench is an ear that uses JSF); we observed them systematically on each of the 4 nodes composing the cluster:
> {noformat}
> 2018-06-27 02:47:07,439 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 72) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-granular.war cache from web container
> 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 75) WFLYCLINF0002: Started client-mappings cache from ejb container
> 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 73) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-default.war cache from web container
> 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started default-server cache from web container
> 2018-06-27 02:47:07,439 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 76) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war cache from web container
> 2018-06-27 02:47:07,578 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 75) WFLYCLINF0002: Started clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 2018-06-27 02:47:07,673 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
> 2018-06-27 02:47:07,713 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
> 2018-06-27 02:47:07,739 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1!
> 2018-06-27 02:47:08,149 SEVERE [javax.enterprise.resource.webcontainer.jsf.flow] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra
> 2018-06-27 02:47:08,163 SEVERE [javax.enterprise.resource.webcontainer.jsf.application.view] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra
> 2018-06-27 02:47:08,586 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 76) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench-granular'
> 2018-06-27 02:47:08,586 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 72) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench'
> 2018-06-27 02:47:08,587 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 78) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench-passivating'
> 2018-06-27 02:47:09,860 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 76) WFLYUT0021: Registered web context: '/clusterbench-granular' for server 'default-server'
> 2018-06-27 02:47:09,863 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/clusterbench' for server 'default-server'
> 2018-06-27 02:47:09,863 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server'
> 2018-06-27 02:47:09,889 INFO [org.jboss.as.server] (ServerService Thread Pool -- 42) WFLYSRV0010: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear")
> 2018-06-27 02:47:09,989 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> {noformat}
>
> Complete log [here|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap...]
> Already observed a very long time ago: https://issues.jboss.org/browse/WFLY-1946
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months