June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4205) DMN: UI enhancements for Data Type editor

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4205: -------------------------------------- Description: *User Story* As a practitioner I want to be able to: * select an existing data type * create a simple or structured data type * create a “compound” (or complex) data type, easily. *  expand/collapse views of compound data types, so that I can___ *  navigate between levels in a compound data type, so that I can___ * edit an existing data type * remove an existing data type  …so that I can use the data type when creating a decision related asset. *Requested UI enhancements, based on user feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)* * * NESTING ISSUES ARE HIGH PRIORITY - Fix Dropdown menu labeling (Structure) - Weird tooltip on Structured row. - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder. - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology. - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu. - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance. - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu RELATED SAVE INTERACTIONS (Save, Delete, Remove) - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model - - It's not obvious that you have to select the "check mark" to commit the change. - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked. OTHER: - “Constraint” link was confusing, but location was good. - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.) - Questions around Save - should it not require Save at the row level. - It feels unnatural to have to click the "Constraints" to open the Constraints modal. was: *User Story* As a practitioner I want to be able to: * select an existing data type * create a simple or structured data type * create a “compound” (or complex) data type, easily. *  expand/collapse views of compound data types, so that I can___ *  navigate between levels in a compound data type, so that I can___ * edit an existing data type * remove an existing data type  …so that I can use the data type when creating a decision related asset. Requested UI enhancements, based on feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic) * NESTING ISSUES ARE HIGH PRIORITY - Fix Dropdown menu labeling (Structure) - Weird tooltip on Structured row. - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder. - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology. - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu. - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance. - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu RELATED SAVE INTERACTIONS (Save, Delete, Remove) - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model - - It's not obvious that you have to select the "check mark" to commit the change. - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked. OTHER: - “Constraint” link was confusing, but location was good. - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.) - Questions around Save - should it not require Save at the row level. - It feels unnatural to have to click the "Constraints" to open the Constraints modal. > DMN: UI enhancements for Data Type editor > ----------------------------------------- > > Key: DROOLS-4205 > URL: https://issues.jboss.org/browse/DROOLS-4205 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > *User Story* > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. > *Requested UI enhancements, based on user feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)* > * * NESTING ISSUES ARE HIGH PRIORITY > - Fix Dropdown menu labeling (Structure) > - Weird tooltip on Structured row. > - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder. > - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology. > - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu. > - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance. > - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu > RELATED SAVE INTERACTIONS (Save, Delete, Remove) > - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model > - - It's not obvious that you have to select the "check mark" to commit the change. > - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked. > OTHER: > - “Constraint” link was confusing, but location was good. > - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.) > - Questions around Save - should it not require Save at the row level. > - It feels unnatural to have to click the "Constraints" to open the Constraints modal. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3819) Rule Units 2.0: evaluate 7.x behavior and consider new design

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3819?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3819: ----------------------------------- Description: I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) *Deliverable*: design document https://docs.google.com/document/d/1adMpinMd9-lWCzY_fbYCVRlitcVtCQAnVlWRG... was: I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) *Deliverable*: design document > Rule Units 2.0: evaluate 7.x behavior and consider new design > ------------------------------------------------------------- > > Key: DROOLS-3819 > URL: https://issues.jboss.org/browse/DROOLS-3819 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) > *Deliverable*: design document https://docs.google.com/document/d/1adMpinMd9-lWCzY_fbYCVRlitcVtCQAnVlWRG... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3819) Rule Units 2.0: evaluate 7.x behavior and consider new design

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3819?page=com.atlassian.jira.plugi... ] Edoardo Vacchi commented on DROOLS-3819: ---------------------------------------- final doc https://docs.google.com/document/d/1adMpinMd9-lWCzY_fbYCVRlitcVtCQAnVlWRG... > Rule Units 2.0: evaluate 7.x behavior and consider new design > ------------------------------------------------------------- > > Key: DROOLS-3819 > URL: https://issues.jboss.org/browse/DROOLS-3819 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) > *Deliverable*: design document -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12255) WFLY does not accept the Narayana's long version of property expiryScannerClassNames to define expiry scanners

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created WFLY-12255: --------------------------------------- Summary: WFLY does not accept the Narayana's long version of property expiryScannerClassNames to define expiry scanners Key: WFLY-12255 URL: https://issues.jboss.org/browse/WFLY-12255 Project: WildFly Issue Type: Bug Components: Transactions Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka The WFLY-951enables the way to set the Narayana settings of the expiry class names via system property. The issue enforces users to use only property in form {{RecoveryEnvironmentBean.expiryScannerClassNames}}. But Narayana provides to use either this shortened version of the property for any configuration option. But it accepts the longer form for property with fully qualified bean class name (https://jbossts.blogspot.com/2018/01/narayana-periodic-recovery-of-xa.htm...). In this case it's {{com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.expiryScannerClassNames}}. That property (which sets the same thing as its shortened version) should be accepted by the WFLY as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4268) FIX XStream configuration

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4268?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-4268: ------------------------------------- Sprint: 2019 Week 26-28 > FIX XStream configuration > ------------------------- > > Key: DROOLS-4268 > URL: https://issues.jboss.org/browse/DROOLS-4268 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Fix XStream defaults to have a generated xml as "plain" as possible (remove "reference" use, remove "class" attribute for list elements) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4552) Upgrade Undertow to 2.0.23.Final

by Teresa Miyar Gil (Jira)

Teresa Miyar Gil created WFCORE-4552: ---------------------------------------- Summary: Upgrade Undertow to 2.0.23.Final Key: WFCORE-4552 URL: https://issues.jboss.org/browse/WFCORE-4552 Project: WildFly Core Issue Type: Component Upgrade Reporter: Teresa Miyar Gil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4428) Upgrade CLI to use aesh 2.4

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFCORE-4428?page=com.atlassian.jira.plugi... ] Jean Francois Denise updated WFCORE-4428: ----------------------------------------- Description: aesh, aesh-readline and aesh-extensions new release (was: aesh, aesh-readline and aesh-extensions have been released with http repositories to resolve artifacts, it needs a new release.) > Upgrade CLI to use aesh 2.4 > --------------------------- > > Key: WFCORE-4428 > URL: https://issues.jboss.org/browse/WFCORE-4428 > Project: WildFly Core > Issue Type: Component Upgrade > Components: CLI > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > aesh, aesh-readline and aesh-extensions new release -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4269) kogito-codegen-tests: alternative testing strategy for codegen

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4269: -------------------------------------- Summary: kogito-codegen-tests: alternative testing strategy for codegen Key: DROOLS-4269 URL: https://issues.jboss.org/browse/DROOLS-4269 Project: Drools Issue Type: Bug Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi Currently we are doing dynamic compilation and classloading to test code generation. I am proposing an alternative strategy that use the plain Maven plugin. - create `kogito-codegen-tests` - write data/rules/process sources under src/main/{java,resources} - write tests under src/test/ tests are now allowed to refer directly to codegenerated classes by name. just use mvn compile test to run the tests caveat: not sure if the maven plugin is picked up from the current source tree or from the SNAPSHOT on the nexus, we need to check this -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12245) Default routing cache in HA profiles should use replicated-cache

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12245?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-12245: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12393, https://github.com/wildfly/wildfly/pull/12399 (was: https://github.com/wildfly/wildfly/pull/12393) > Default routing cache in HA profiles should use replicated-cache > ---------------------------------------------------------------- > > Key: WFLY-12245 > URL: https://issues.jboss.org/browse/WFLY-12245 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 17.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4268) FIX XStream configuration

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4268: ---------------------------------------- Summary: FIX XStream configuration Key: DROOLS-4268 URL: https://issues.jboss.org/browse/DROOLS-4268 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Fix XStream defaults to have a generated xml as "plain" as possible (remove "reference" use, remove "class" attribute for list elements) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2019