[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-2728 at 7/12/18 9:13 AM:
---------------------------------------------------------------------
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)}}
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)}}
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
was (Author: karreiro):
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
- Person
- name (String)
- age (Number)
- email (String)
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-2728 at 7/12/18 9:13 AM:
---------------------------------------------------------------------
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
{{
- Person
- name (String)
- age (Number)
- email (String)
}}
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)}}
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
was (Author: karreiro):
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)}}
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)}}
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2728:
---------------------------------------
Attachment: Screen Shot 2018-07-12 at 9.41.40 AM.png
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-2728:
--------------------------------------------
[~uxdlc], thank you for the prototypes :-)
I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:
1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
!Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail!
Am I missing something?
2) Structured data type
Here the user can create a complex type with fields, something like this:
- Person
- name (String)
- age (Number)
- email (String)
I think that this prototype refers to this scenario:
!Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail!
However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".
WDYT?
3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
- Person
- name (String)
- age (Number)
- email (String)
- address
- street (String)
- house_number (Number)
- city_name (String)
How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?
Thanks again, Liz.
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2728:
---------------------------------------
Attachment: Screen Shot 2018-07-12 at 9.41.34 AM.png
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2733) Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
by Luca Molteni (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2733?page=com.atlassian.jira.plugi... ]
Luca Molteni updated DROOLS-2733:
---------------------------------
Description:
The executable model doesn't support custom inline accumulate code that uses external declarations such as
{code:java}
String str = "import " + Person.class.getCanonicalName() + ";\n" +
"rule R dialect \"mvel\" when\n" +
" String( $l : length )" +
" $sum : Integer() from accumulate (\n" +
" Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
" )" +
"then\n" +
" insert($sum);\n" +
"end";
{code}
(Notice that in the init we multiply the sum value with the length of string)
But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
Probably what we should do instead is putting MVEL expressions in the DSL directly such as
{code:java}
accumulateScript("initCode", "accCode", "reverseCode");
{code}
and then during interpretation create a new MVEL context and execute the accumulate in memory
See
AccumulateUnsupportedTest.testMVELAccumulate
AccumulateUnsupportedTest.testMVELAccumulate2WM
was:
The executable model doesn't support custom inline accumulate code that uses external declarations such as
{code:java}
String str = "import " + Person.class.getCanonicalName() + ";\n" +
"rule R dialect \"mvel\" when\n" +
" String( $l : length )" +
" $sum : Integer() from accumulate (\n" +
" Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
" )" +
"then\n" +
" insert($sum);\n" +
"end";
{code}
(Notice that in the init we multiply the sum value with the length of string)
But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
Probably what we should do instead is putting MVEL expressions in the DSL directly such as
{code:java}
accumulateScript("initCode", "accCode", "reverseCode");
{code}
and then during interpretation create a new MVEL context and execute the accumulate in memory
See AccumulateUnsupportedTest.testMVELAccumulate
> Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
> -----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2733
> URL: https://issues.jboss.org/browse/DROOLS-2733
> Project: Drools
> Issue Type: Feature Request
> Components: executable model
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Optional
>
> The executable model doesn't support custom inline accumulate code that uses external declarations such as
> {code:java}
> String str = "import " + Person.class.getCanonicalName() + ";\n" +
> "rule R dialect \"mvel\" when\n" +
> " String( $l : length )" +
> " $sum : Integer() from accumulate (\n" +
> " Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
> " )" +
> "then\n" +
> " insert($sum);\n" +
> "end";
> {code}
> (Notice that in the init we multiply the sum value with the length of string)
> But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
> This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
> Probably what we should do instead is putting MVEL expressions in the DSL directly such as
> {code:java}
> accumulateScript("initCode", "accCode", "reverseCode");
> {code}
> and then during interpretation create a new MVEL context and execute the accumulate in memory
> See
> AccumulateUnsupportedTest.testMVELAccumulate
> AccumulateUnsupportedTest.testMVELAccumulate2WM
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2733) Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
by Luca Molteni (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2733?page=com.atlassian.jira.plugi... ]
Luca Molteni updated DROOLS-2733:
---------------------------------
Description:
The executable model doesn't support custom inline accumulate code that uses external declarations such as
{code:java}
String str = "import " + Person.class.getCanonicalName() + ";\n" +
"rule R dialect \"mvel\" when\n" +
" String( $l : length )" +
" $sum : Integer() from accumulate (\n" +
" Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
" )" +
"then\n" +
" insert($sum);\n" +
"end";
{code}
(Notice that in the init we multiply the sum value with the length of string)
But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
Probably what we should do instead is putting MVEL expressions in the DSL directly such as
{code:java}
accumulateScript("initCode", "accCode", "reverseCode");
{code}
and then during interpretation create a new MVEL context and execute the accumulate in memory
See AccumulateUnsupportedTest.testMVELAccumulate
was:
The executable model doesn't support custom inline accumulate code that uses external declarations such as
{code:java}
String str = "import " + Person.class.getCanonicalName() + ";\n" +
"rule R dialect \"mvel\" when\n" +
" String( $l : length )" +
" $sum : Integer() from accumulate (\n" +
" Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
" )" +
"then\n" +
" insert($sum);\n" +
"end";
{code}
(Notice that in the init we multiply the sum value with the length of string)
But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
Probably what we should do instead is putting MVEL expressions in the DSL directly such as
{code:java}
accumulateScript("initCode", "accCode", "reverseCode");
{code}
and then during interpretation create a new MVEL context and execute the accumulate in memory
> Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
> -----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2733
> URL: https://issues.jboss.org/browse/DROOLS-2733
> Project: Drools
> Issue Type: Feature Request
> Components: executable model
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Optional
>
> The executable model doesn't support custom inline accumulate code that uses external declarations such as
> {code:java}
> String str = "import " + Person.class.getCanonicalName() + ";\n" +
> "rule R dialect \"mvel\" when\n" +
> " String( $l : length )" +
> " $sum : Integer() from accumulate (\n" +
> " Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
> " )" +
> "then\n" +
> " insert($sum);\n" +
> "end";
> {code}
> (Notice that in the init we multiply the sum value with the length of string)
> But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
> This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
> Probably what we should do instead is putting MVEL expressions in the DSL directly such as
> {code:java}
> accumulateScript("initCode", "accCode", "reverseCode");
> {code}
> and then during interpretation create a new MVEL context and execute the accumulate in memory
> See AccumulateUnsupportedTest.testMVELAccumulate
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3962) Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ]
Matej Novotny updated WFCORE-3962:
----------------------------------
Description:
As per request, copying MODULES-372 to WFCORE as well.
Starting WFLY with JDK 11 using {{standalone.sh}} yields:
{code}
org.jboss.modules.ModuleNotFoundException: java.se
at org.jboss.modules.Module.addPaths(Module.java:1266)
at org.jboss.modules.Module.link(Module.java:1622)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
at org.jboss.modules.Main.main(Main.java:437)
{code}
Output of {{java -version}}:
{code}
openjdk version "11-ea" 2018-09-25
OpenJDK Runtime Environment 18.9 (build 11-ea+21)
OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
{code}
was:
As per request, copying MODULES-372 to WFCORE as well.
Starting WFLY with JDK 11 using {{standalone.sh}} yields:
{code}
org.jboss.modules.ModuleNotFoundException: java.se
at org.jboss.modules.Module.addPaths(Module.java:1266)
at org.jboss.modules.Module.link(Module.java:1622)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
at org.jboss.modules.Main.main(Main.java:437)
{code}
> Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se
> -----------------------------------------------------------------------
>
> Key: WFCORE-3962
> URL: https://issues.jboss.org/browse/WFCORE-3962
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules
> Affects Versions: 6.0.0.Alpha3
> Reporter: Matej Novotny
> Assignee: David Lloyd
> Labels: Java11
>
> As per request, copying MODULES-372 to WFCORE as well.
> Starting WFLY with JDK 11 using {{standalone.sh}} yields:
> {code}
> org.jboss.modules.ModuleNotFoundException: java.se
> at org.jboss.modules.Module.addPaths(Module.java:1266)
> at org.jboss.modules.Module.link(Module.java:1622)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> at org.jboss.modules.Main.main(Main.java:437)
> {code}
> Output of {{java -version}}:
> {code}
> openjdk version "11-ea" 2018-09-25
> OpenJDK Runtime Environment 18.9 (build 11-ea+21)
> OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years