[JBoss JIRA] (DROOLS-1976) [DMN Editor] Check that unique node names are enforced
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1976?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-1976:
----------------------------------
Fix Version/s: (was: 7.5.0.Final)
> [DMN Editor] Check that unique node names are enforced
> ------------------------------------------------------
>
> Key: DROOLS-1976
> URL: https://issues.jboss.org/browse/DROOLS-1976
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Labels: reported-by-qe
>
> According to the DMN specification, all node names represents also variable names, thus it is needed to enforce unique node name in the DRD diagram.
> Acceptance criteria of this task:
> - Verify if DMN editor enforce unique node names
> -- ?Prepare test scenarios?
> - If it doesn't, file jira that will ensure fix of this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-1937) [DMN Editor] Dynamic Form Properties with nested hierarchy binds to wrong object/widget
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1937?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-1937:
----------------------------------
Fix Version/s: (was: 7.5.0.Final)
> [DMN Editor] Dynamic Form Properties with nested hierarchy binds to wrong object/widget
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-1937
> URL: https://issues.jboss.org/browse/DROOLS-1937
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Roger Martínez
> Priority: Critical
> Labels: Stunner
>
> The Dynamic Form generated from a nested object hierarchy binds objects/widgets to the incorrect instances. For example; the below classes define an {{Id}} form field that is used in both {{InputData}} (through inheritance) and {{InformationItem}} (through sub-form reference and inheritance). When changing the {{Id}} field (for example) in the {{InputData}} form property the "Id" value of the nested "Information Item" is updated.
> {code}
> public abstract class DMNModelInstrumentedBase implements DMNDefinition {
>
> //No @FormFields etc
>
> }
>
> public abstract class DMNElement extends DMNModelInstrumentedBase {
>
> @Property
> @FormField
> protected Id id;
>
> @Property
> @FormField(afterElement = "id")
> protected Label label;
>
> @Property
> @FormField(afterElement = "label")
> protected Description description;
>
> ....
> }
>
> public abstract class NamedElement extends DMNElement {
>
> @Property
> @FormField(afterElement = "description")
> protected Name name;
>
> ....
> }
>
> @FormDefinition(policy = FieldPolicy.ONLY_MARKED)
> public class InformationItem extends NamedElement implements DMNPropertySet {
>
> @Property
> @FormField(afterElement = "name")
> protected QName typeRef;
>
> ....
> }
> public abstract class DRGElement extends NamedElement {}
> @FormDefinition(policy = FieldPolicy.ONLY_MARKED)
> public class InputData extends DRGElement {
> ...
> @PropertySet
> @FormField(afterElement = "name")
> protected InformationItem variable;
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months