[JBoss JIRA] (DROOLS-2214) [DMN Editor] Content of the decision node is not copied
by Roger Martínez (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2214?page=com.atlassian.jira.plugi... ]
Roger Martínez commented on DROOLS-2214:
----------------------------------------
Hey [~manstis] [~tdolphine]
Well not sure if DMN is actually being included/delivered in the workbench... probably better letting [~manstis] decide what's next step here :) I would vote for not disabling it, just implementing the missing additional capabilities for cloning more metadata... but up to you guys, not even sure what are the requirements for the DMN editor.
> [DMN Editor] Content of the decision node is not copied
> -------------------------------------------------------
>
> Key: DROOLS-2214
> URL: https://issues.jboss.org/browse/DROOLS-2214
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: Stunner
>
> User has possibility to copy a DRG node by a CTRL+C shortcut, however the problem is that content of the node is not copied.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2214) [DMN Editor] Content of the decision node is not copied
by Tiago Dolphine (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2214?page=com.atlassian.jira.plugi... ]
Tiago Dolphine commented on DROOLS-2214:
----------------------------------------
The relationship between nodes are being handled on the CloneNodeCommand, this can be extended to add custom logic, or if we decided that this could be handled by the default clone command we can add there. The CloneManager is handling only the properties values cloning.
I don't know a lot about the DMN but I can try to take this issue, what do you think [~roger600] [~manstis] ?
Anyway if the copy/paste is not expected on the DMN now, we can disable it for the DMN until we get this issue resolved.
> [DMN Editor] Content of the decision node is not copied
> -------------------------------------------------------
>
> Key: DROOLS-2214
> URL: https://issues.jboss.org/browse/DROOLS-2214
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: Stunner
>
> User has possibility to copy a DRG node by a CTRL+C shortcut, however the problem is that content of the node is not copied.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9598) Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing support
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9598?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-9598:
---------------------------------
Summary: Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing support (was: Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing)
> Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing support
> ---------------------------------------------------------------------------
>
> Key: WFLY-9598
> URL: https://issues.jboss.org/browse/WFLY-9598
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Test Suite
> Affects Versions: 11.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 12.0.0.Alpha1
>
>
> Goals
> * simplify test development
> * make the testsuite manageable again
> * lower execution time
> Steps to take
> * move the testsuite away from using XSLT and just rely on the CLI scripts
> * provide utility for configuring servers using CLI
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2214) [DMN Editor] Content of the decision node is not copied
by Roger Martínez (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2214?page=com.atlassian.jira.plugi... ]
Roger Martínez commented on DROOLS-2214:
----------------------------------------
Hey [~manstis]
This is a brand new feature released just a few weeks ago, tbh I don't know the details for it yet.. so would be nice if [~tdolphine] can give us that information, pleaseee :)
Where you think [~tdolphine] should be the best point to provide additional capabilities for the copy/paste here, probably creating an specialization for the CloneManager? Or being able to provide different clone logics from the different PropertySets (a default one for BPMN, but DMN can for example provide its own)... Thanks!
> [DMN Editor] Content of the decision node is not copied
> -------------------------------------------------------
>
> Key: DROOLS-2214
> URL: https://issues.jboss.org/browse/DROOLS-2214
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: Stunner
>
> User has possibility to copy a DRG node by a CTRL+C shortcut, however the problem is that content of the node is not copied.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-1937) [DMN Editor] Dynamic Form Properties with nested hierarchy binds to wrong object/widget
by Roger Martínez (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1937?page=com.atlassian.jira.plugi... ]
Roger Martínez commented on DROOLS-1937:
----------------------------------------
Hey [~manstis]
Just asked for a configuration change in the Stunner's JIRA agile board in order to show this ticket and be able to give it priority and so assign to someone. Sorry about the inconveniences, will start with it ASAP! Thanks!
> [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, 3 months
[JBoss JIRA] (WFLY-5410) jboss-web_10_0.xsd is inccorect
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5410?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-5410:
----------------------------------------
[~ehugonnet] is JBMETA-389 done?
> jboss-web_10_0.xsd is inccorect
> -------------------------------
>
> Key: WFLY-5410
> URL: https://issues.jboss.org/browse/WFLY-5410
> Project: WildFly
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.0.0.CR2
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
>
> jboss-web_10_0.xsd requires an extension of javaee 7 xsd in the jboss namespace for <xsd:group ref="jboss:jndiEnvironmentRefsGroup"/>.
> This was in jboss_commons_6_0.xsd for Javaee 6 so we need to have a similar schema for Javaee 7and import it in jboss-web_10_0.xsd.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months