[JBoss JIRA] (WFCORE-4553) Logging on IBM Java doesn't create log
by Vratislav Marek (Jira)
[ https://issues.jboss.org/browse/WFCORE-4553?page=com.atlassian.jira.plugi... ]
Vratislav Marek updated WFCORE-4553:
------------------------------------
Description:
On application output found:
{code}
Bad level value for property: handler.CLIFILE.level
{code}
handler.CLIFILE.level is the name of a property from the test property file used in standalone testsuite
Stack trace:
{code}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.jboss.as.test.integration.management.cli.SilentModeTestCase.checkIfEmpty(SilentModeTestCase.java:152)
at org.jboss.as.test.integration.management.cli.SilentModeTestCase.testLogging(SilentModeTestCase.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
{code}
was:
On application output found:
{code}
Bad level value for property: handler.CLIFILE.level
{code}
Stack trace:
{code}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.jboss.as.test.integration.management.cli.SilentModeTestCase.checkIfEmpty(SilentModeTestCase.java:152)
at org.jboss.as.test.integration.management.cli.SilentModeTestCase.testLogging(SilentModeTestCase.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
{code}
Summary: Logging on IBM Java doesn't create log (was: Test logging on IBM Java doesn't create log)
> Logging on IBM Java doesn't create log
> --------------------------------------
>
> Key: WFCORE-4553
> URL: https://issues.jboss.org/browse/WFCORE-4553
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Environment: * IBM Java 1.8
> * RHEL6 & RHEL7
> Reporter: Vratislav Marek
> Assignee: James Perkins
> Priority: Major
>
> On application output found:
> {code}
> Bad level value for property: handler.CLIFILE.level
> {code}
> handler.CLIFILE.level is the name of a property from the test property file used in standalone testsuite
> Stack trace:
> {code}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.as.test.integration.management.cli.SilentModeTestCase.checkIfEmpty(SilentModeTestCase.java:152)
> at org.jboss.as.test.integration.management.cli.SilentModeTestCase.testLogging(SilentModeTestCase.java:99)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFCORE-4553) Test logging on IBM Java doesn't create log
by Vratislav Marek (Jira)
Vratislav Marek created WFCORE-4553:
---------------------------------------
Summary: Test logging on IBM Java doesn't create log
Key: WFCORE-4553
URL: https://issues.jboss.org/browse/WFCORE-4553
Project: WildFly Core
Issue Type: Bug
Components: Logging
Environment: * IBM Java 1.8
* RHEL6 & RHEL7
Reporter: Vratislav Marek
Assignee: James Perkins
On application output found:
{code}
Bad level value for property: handler.CLIFILE.level
{code}
Stack trace:
{code}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.jboss.as.test.integration.management.cli.SilentModeTestCase.checkIfEmpty(SilentModeTestCase.java:152)
at org.jboss.as.test.integration.management.cli.SilentModeTestCase.testLogging(SilentModeTestCase.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[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 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.
> 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)
6 years, 3 months
[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 commented on DROOLS-4205:
-------------------------------------------
[~sarahjane] [~aglass] I added the key take-aways from the work you did on DROOLS-3944. If there's anything I missed, please add it to this jira in the next few days if possible. :) Thanks!
> 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)
6 years, 3 months
[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)
6 years, 3 months
[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)
6 years, 3 months
[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)
6 years, 3 months