[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)
7 years, 1 month
[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)
7 years, 1 month
[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)
7 years, 1 month
[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 updated DROOLS-2949:
--------------------------------
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*
was:
- 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
> [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)
7 years, 1 month
[JBoss JIRA] (DROOLS-2949) [DMN Designer] Change of data type is not propagated to manage dialog
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2949:
-----------------------------------
Summary: [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
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)
7 years, 1 month
[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
- 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)
-
- 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
> - Build and deploy after structure change
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[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)
-
- Edit multiple items in parallel
- 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
- 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)
> -
> - Edit multiple items in parallel
> - Build and deploy after structure change
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[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:
------------------------------------------
Workaround Description:
One workaround is to change the modules manually, placing the jaeger-thrift JAR within the same module as jaeger-core, and changing the module definition.
Copy the JAR:
{code}
cp modules/system/layers/base/io/jaegertracing/jaeger-thrift/main/jaeger-thrift-0.30.6.jar modules/system/layers/base/io/jaegertracing/jaeger-core/main/
{code}
Module definition at modules/system/layers/base/io/jaegertracing/jaeger-core/main/module.xml:
{code}
<module name="io.jaegertracing.jaeger-core" xmlns="urn:jboss:module:1.8">
<properties>
<property name="jboss.api" value="private"/>
</properties>
<resources>
<resource-root path="jaeger-core-0.30.6.jar"/>
<resource-root path="jaeger-thrift-0.30.6.jar"/>
</resources>
<dependencies>
<module name="com.google.code.gson"/>
<module name="io.opentracing.opentracing-api"/>
<module name="io.opentracing.opentracing-util"/>
<module name="org.apache.thrift"/>
<module name="org.slf4j"/>
</dependencies>
</module>
{code}
Additionally, the module org.wildfly.microprofile.opentracing-smallrye (modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/module.xml) should have the references to both the Apache Thrift and Jaeger Thrift removed.
A second workaround is to have the deployed artifact to embed the Jaeger Client artifact, along with a Tracer Factory. A reference can be found on Jaeger Client Java repository:
https://github.com/jaegertracing/jaeger-client-java/blob/8e9492fcc57fcf30...
was:
One workaround is to change the modules manually, placing the jaeger-thrift JAR within the same module as jaeger-core, and changing the module definition.
Copy the JAR:
{code}
cp modules/system/layers/base/io/jaegertracing/jaeger-thrift/main/jaeger-thrift-0.30.6.jar modules/system/layers/base/io/jaegertracing/jaeger-core/main/
{code}
Module definition at modules/system/layers/base/io/jaegertracing/jaeger-core/main/module.xml:
{code}
<module name="io.jaegertracing.jaeger-core" xmlns="urn:jboss:module:1.8">
<properties>
<property name="jboss.api" value="private"/>
</properties>
<resources>
<resource-root path="jaeger-core-0.30.6.jar"/>
<resource-root path="jaeger-thrift-0.30.6.jar"/>
</resources>
<dependencies>
<module name="com.google.code.gson"/>
<module name="io.opentracing.opentracing-api"/>
<module name="io.opentracing.opentracing-util"/>
<module name="org.apache.thrift"/>
<module name="org.slf4j"/>
</dependencies>
</module>
{code}
Additionally, the module org.wildfly.microprofile.opentracing-smallrye should have the references to both the Apache Thrift and Jaeger Thrift removed.
A second workaround is to have the deployed artifact to embed the Jaeger Client artifact, along with a Tracer Factory. A reference can be found on Jaeger Client Java repository:
https://github.com/jaegertracing/jaeger-client-java/blob/8e9492fcc57fcf30...
> 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 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)
7 years, 1 month
[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:
------------------------------------------
Workaround Description:
One workaround is to change the modules manually, placing the jaeger-thrift JAR within the same module as jaeger-core, and changing the module definition.
Copy the JAR:
{code}
cp modules/system/layers/base/io/jaegertracing/jaeger-thrift/main/jaeger-thrift-0.30.6.jar modules/system/layers/base/io/jaegertracing/jaeger-core/main/
{code}
Module definition at modules/system/layers/base/io/jaegertracing/jaeger-core/main/module.xml:
{code}
<module name="io.jaegertracing.jaeger-core" xmlns="urn:jboss:module:1.8">
<properties>
<property name="jboss.api" value="private"/>
</properties>
<resources>
<resource-root path="jaeger-core-0.30.6.jar"/>
<resource-root path="jaeger-thrift-0.30.6.jar"/>
</resources>
<dependencies>
<module name="com.google.code.gson"/>
<module name="io.opentracing.opentracing-api"/>
<module name="io.opentracing.opentracing-util"/>
<module name="org.apache.thrift"/>
<module name="org.slf4j"/>
</dependencies>
</module>
{code}
Additionally, the module org.wildfly.microprofile.opentracing-smallrye should have the references to both the Apache Thrift and Jaeger Thrift removed.
A second workaround is to have the deployed artifact to embed the Jaeger Client artifact, along with a Tracer Factory. A reference can be found on Jaeger Client Java repository:
https://github.com/jaegertracing/jaeger-client-java/blob/8e9492fcc57fcf30...
was:
One workaround is to change the modules manually, placing the jaeger-thrift JAR within the same module as jaeger-core, and changing the module definition.
Copy the JAR:
{code}
cp modules/system/layers/base/io/jaegertracing/jaeger-thrift/main/jaeger-thrift-0.30.6.jar modules/system/layers/base/io/jaegertracing/jaeger-core/main/
{code}
Module definition:
{code}
<module name="io.jaegertracing.jaeger-core" xmlns="urn:jboss:module:1.8">
<properties>
<property name="jboss.api" value="private"/>
</properties>
<resources>
<resource-root path="jaeger-core-0.30.6.jar"/>
<resource-root path="jaeger-thrift-0.30.6.jar"/>
</resources>
<dependencies>
<module name="com.google.code.gson"/>
<module name="io.opentracing.opentracing-api"/>
<module name="io.opentracing.opentracing-util"/>
<module name="org.apache.thrift"/>
<module name="org.slf4j"/>
</dependencies>
</module>
{code}
Additionally, the module org.wildfly.microprofile.opentracing-smallrye should have the references to both the Apache Thrift and Jaeger Thrift removed.
A second workaround is to have the deployed artifact to embed the Jaeger Client artifact, along with a Tracer Factory. A reference can be found on Jaeger Client Java repository:
https://github.com/jaegertracing/jaeger-client-java/blob/8e9492fcc57fcf30...
> 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 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)
7 years, 1 month