[JBoss JIRA] (DROOLS-2654) [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2654?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2654:
--------------------------------
Description:
When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
[~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
h3. Manual Acceptance test
For each column/row agreed in comments that should support this feature:
- Append row/column, fill name, save reopen, check value stored
- Append such row/column that could affect name in DRG, fill name, check DRG and rename there, check expression editor again
- Try undo/redo after appending row/column (x)
- Add multiple items in row, check always the last is edited
was:
When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
[~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
h3. Manual Acceptance test
For each column/row agreed in comments that should support this feature:
- Append row/column, fill name, save reopen, check value stored
- Append such row/column that could affect name in DRG, fill name, check DRG and rename there, check expression editor again
- Try undo/redo after appending row/column
- Add multiple items in row, check always the last is edited
> [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-2654
> URL: https://issues.jboss.org/browse/DROOLS-2654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Labels: UX, UXTeam
>
> When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
> [~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
> h3. Manual Acceptance test
> For each column/row agreed in comments that should support this feature:
> - Append row/column, fill name, save reopen, check value stored
> - Append such row/column that could affect name in DRG, fill name, check DRG and rename there, check expression editor again
> - Try undo/redo after appending row/column (x)
> - Add multiple items in row, check always the last is edited
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2711) [IE] Package dropdown is broken in new asset dialogs
by Toni Rikkola (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2711?page=com.atlassian.jira.plugi... ]
Toni Rikkola moved RHPAM-1351 to DROOLS-2711:
---------------------------------------------
Project: Drools (was: Red Hat Process Automation Manager)
Key: DROOLS-2711 (was: RHPAM-1351)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: Guided Rule Editor
(was: Business Central)
Affects Version/s: (was: 7.0.0.GA)
QE Status: NEW
> [IE] Package dropdown is broken in new asset dialogs
> ----------------------------------------------------
>
> Key: DROOLS-2711
> URL: https://issues.jboss.org/browse/DROOLS-2711
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Environment: latest 7.7.0 snapshot, Internet Explorer
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Labels: AppFormer
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2654) [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2654?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2654:
--------------------------------
Description:
When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
[~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
h3. Manual Acceptance test
For each column/row agreed in comments that should support this feature:
- Append row/column, fill name, save reopen, check value stored
- Append such row/column that could affect name in DRG, fill name, check DRG and rename there, check expression editor again
- Try undo/redo after appending row/column
- Add multiple items in row, check always the last is edited
was:
When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
[~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
h3. Manual Acceptance test
For each column/row agreed in comments that should support this feature:
- Append row/column, fill name, save reopen, check value stored
- Append such row/column that could affect name in DRG, fill name, check DRG and rename there, check expression editor again
- Try undo/redo after appending row/column
> [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-2654
> URL: https://issues.jboss.org/browse/DROOLS-2654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Labels: UX, UXTeam
>
> When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
> [~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
> h3. Manual Acceptance test
> For each column/row agreed in comments that should support this feature:
> - Append row/column, fill name, save reopen, check value stored
> - Append such row/column that could affect name in DRG, fill name, check DRG and rename there, check expression editor again
> - Try undo/redo after appending row/column
> - Add multiple items in row, check always the last is edited
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)
by Klara Kufova (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ]
Klara Kufova commented on DROOLS-2706:
--------------------------------------
I vote for *Scenario Simulation*.
> New "Scenario Test" asset list option (UX)
> ------------------------------------------
>
> Key: DROOLS-2706
> URL: https://issues.jboss.org/browse/DROOLS-2706
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor.
> *Verification conditions:*
> The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.)
> Notes:
> Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10325) Test Suite: Integration - Web failures against wildfly-dist
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10325?page=com.atlassian.jira.plugin... ]
Petr Kremensky closed WFLY-10325.
---------------------------------
Resolution: Done
> Test Suite: Integration - Web failures against wildfly-dist
> -----------------------------------------------------------
>
> Key: WFLY-10325
> URL: https://issues.jboss.org/browse/WFLY-10325
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Assignee: Jan Stourac
>
> Web integration tests fail if runs against wildfly-dist distribution - via jboss.dist property (the property is used to run the tests against productized builds or patched EAP distributions).
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -DskipTests
> cd testsuite
> mvn test -B -pl integration/web/
> # Tests run: 112, Failures: 0, Errors: 0, Skipped: 3
> mvn test -B -pl integration/web/ -Djboss.dist=$(realpath ../dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT)
> # Tests run: 109, Failures: 4, Errors: 9, Skipped: 3
> {noformat}
> There seems to be an issue with *WebCERTTestsSetup*, as once I enable the logs ( -DtestLogToFile=false ), the following errors appear.
> {noformat}
> 10:57:09,622 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "ssl-cert-realm")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.ssl-cert-realm.key-manager" => "Failed to start service
> Caused by: java.lang.IllegalStateException: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore"},
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10325) Test Suite: Integration - Web failures against wildfly-dist
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10325?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-10325:
---------------------------------------
This one is no longer an issue. Not sure which commit fixed this, but from the jobs history it has to be something between:
cf8f1bf first good build 2018-06-28
<->
1bf993b last bad build 2018-06-26
> Test Suite: Integration - Web failures against wildfly-dist
> -----------------------------------------------------------
>
> Key: WFLY-10325
> URL: https://issues.jboss.org/browse/WFLY-10325
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Assignee: Jan Stourac
>
> Web integration tests fail if runs against wildfly-dist distribution - via jboss.dist property (the property is used to run the tests against productized builds or patched EAP distributions).
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -DskipTests
> cd testsuite
> mvn test -B -pl integration/web/
> # Tests run: 112, Failures: 0, Errors: 0, Skipped: 3
> mvn test -B -pl integration/web/ -Djboss.dist=$(realpath ../dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT)
> # Tests run: 109, Failures: 4, Errors: 9, Skipped: 3
> {noformat}
> There seems to be an issue with *WebCERTTestsSetup*, as once I enable the logs ( -DtestLogToFile=false ), the following errors appear.
> {noformat}
> 10:57:09,622 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "ssl-cert-realm")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.ssl-cert-realm.key-manager" => "Failed to start service
> Caused by: java.lang.IllegalStateException: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore"},
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3829) ReloadRedirectTestCase#testRedirectWithSecurityCommands fails on IBM JDK
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3829?page=com.atlassian.jira.plugi... ]
Petr Kremensky commented on WFCORE-3829:
----------------------------------------
[~jdenise] sorry, I missed this one. The tests fails no more, thanks for the fix!
> ReloadRedirectTestCase#testRedirectWithSecurityCommands fails on IBM JDK
> ------------------------------------------------------------------------
>
> Key: WFCORE-3829
> URL: https://issues.jboss.org/browse/WFCORE-3829
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Test Suite
> Affects Versions: 5.0.0.Alpha7
> Reporter: Petr Kremensky
> Assignee: Jean-Francois Denise
> Fix For: 6.0.0.Alpha1
>
>
> I tried to run the CLI command from failing assertion manually and it does seem to work as expected, so this more like the testing code problem than functional issue.
> *reproduce*
> {noformat}
> ...wildfly-core] $ mvn clean test -Dtest=ReloadRedirectTestCase#testRedirectWithSecurityCommands -DallTests -pl testsuite/manualmode
> ...
> [INFO] Running org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 33.474 s <<< FAILURE! - in org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase
> [ERROR] testRedirectWithSecurityCommands(org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase) Time elapsed: 22.653 s <<< FAILURE!
> java.lang.AssertionError: No certificate prompt
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase.testRedirectWithSecurityCommands(ReloadRedirectTestCase.java:269)
> ...
> {noformat}
> *environment*
> {noformat}
> $ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> c0847897a3
> {noformat}
> *qa note*
> The test fail causes some other failures in manualmode module:
> org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase.testRedirectWithSecurityCommands
> org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase.testReloadwithRedirect
> org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.testRightVaultPassword
> org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase.testTrustedCLICertificate
> org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.testHTTPS
> org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.testHTTP
> org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.testHTTPSWithCredentialReference
> *ibm jdk download*
> https://developer.ibm.com/javasdk/downloads/sdk8/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-6173) Classes not unloaded after undeployment
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-6173?page=com.atlassian.jira.plugin.... ]
Martin Kouba commented on WFLY-6173:
------------------------------------
[~rahamathjamal] see previous comments, esp. this one: https://issues.jboss.org/browse/WFLY-6173?focusedCommentId=13305859&page=...
> Classes not unloaded after undeployment
> ---------------------------------------
>
> Key: WFLY-6173
> URL: https://issues.jboss.org/browse/WFLY-6173
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 8.2.0.Final, 10.0.0.Final
> Reporter: Joey Wang
> Assignee: Martin Kouba
> Priority: Blocker
> Attachments: Screen Shot 2016-10-27 at 08.04.12.png, Screen Shot 2016-10-27 at 08.15.27.png, memory-leak.zip, memory-leak_New.zip
>
>
> I deployed a small web application with one single JSF and one managed bean, accessed the page and then undeployed the application. I found the classes of this application had never been unloaded via monitoring with Java VistualVM, also using '-XX:+TraceClassUnloading' JVM option proved the classes not unloaded.
> Then checking the heap dump of it, I found there were instance for each enum item (the managed bean has one enum type field, which is always initialized when the managed bean constructed) and one array instance including these enum instances.
> Please refer to the attachment for the same application. I started to verify the classloader memory leak issue because we found hot redeployment of our real application swallow some memory each time, then after lots of redeployment the server was short of memories.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years