[JBoss JIRA] (WFLY-3068) could fail more gracefully when wrong Java version used
by Katarina Hermanova (Jira)
[ https://issues.redhat.com/browse/WFLY-3068?page=com.atlassian.jira.plugin... ]
Katarina Hermanova closed WFLY-3068.
------------------------------------
Resolution: Out of Date
> could fail more gracefully when wrong Java version used
> -------------------------------------------------------
>
> Key: WFLY-3068
> URL: https://issues.redhat.com/browse/WFLY-3068
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading, Server
> Affects Versions: 8.0.0.Final
> Environment: Java version < 7
> Reporter: dpocock
> Assignee: Katarina Hermanova
> Priority: Minor
>
> If I try to start Wildfly with Java 6 (which is no longer support of course) it just fails with a stack:
> 09:51:00,536 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
> 09:51:00,543 WARN [org.jboss.modules] (main) Failed to define class org.jboss.as.jmx.PluggableMBeanServerBuilder in Module "org.jboss.as.jmx:main" from local module loader @36b60b93 (finder: local module finder @69b1fbf4 ()): java.lang.UnsupportedClassVersionError: org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_26]
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [rt.jar:1.6.0_26]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [rt.jar:1.6.0_26]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.Module.loadModuleClass(Module.java:548) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) [jboss-modules.jar:1.3.0.Final]
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:423) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:465) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:511) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:298) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:213) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:174) [rt.jar:1.6.0_26]
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302) [rt.jar:1.6.0_26]
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504) [rt.jar:1.6.0_26]
> at org.jboss.modules.Main.main(Main.java:449) [jboss-modules.jar:1.3.0.Final]
> Exception in thread "main" java.lang.UnsupportedClassVersionError: org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
> at org.jboss.modules.Module.loadModuleClass(Module.java:548)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:423)
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:465)
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:511)
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:298)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:213)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:174)
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
> at org.jboss.modules.Main.main(Main.java:449)
> It would be more friendly if it checked the Java version in the main() function and stopped gracefully. The stack trace is not hard to understand but may not be obvious to everybody.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-12586) Duplicated classes in testsuite, content slightly differs in some cases
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-12586?page=com.atlassian.jira.plugi... ]
Lin Gao updated WFLY-12586:
---------------------------
Description:
There are duplicated classes in testsuite, content slightly differs in some cases
{code}
for i in `find . | grep '.*src.*\.java$' | sed "s,.*src/main/java/,,g" | sed "s,.*src/test/java/,,g" | sort | uniq -c | sort -n | grep "2 " | cut -d" " -f 5-`; do echo "$i"; find . | grep "$i"; echo ""; done
org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
./integration/web/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
./integration/web/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
./integration/ws/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
org/jboss/as/test/integration/web/security/SecuredServlet.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
{code}
was:
+underlined text+There are duplicated classes in testsuite, content slightly differs in some cases
{code}
for i in `find . | grep '.*src.*\.java$' | sed "s,.*src/main/java/,,g" | sed "s,.*src/test/java/,,g" | sort | uniq -c | sort -n | grep "2 " | cut -d" " -f 5-`; do echo "$i"; find . | grep "$i"; echo ""; done
org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
./integration/web/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
./integration/web/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
./integration/ws/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
org/jboss/as/test/integration/web/security/SecuredServlet.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
{code}
> Duplicated classes in testsuite, content slightly differs in some cases
> -----------------------------------------------------------------------
>
> Key: WFLY-12586
> URL: https://issues.redhat.com/browse/WFLY-12586
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Rostislav Svoboda
> Priority: Major
>
> There are duplicated classes in testsuite, content slightly differs in some cases
> {code}
> for i in `find . | grep '.*src.*\.java$' | sed "s,.*src/main/java/,,g" | sed "s,.*src/test/java/,,g" | sort | uniq -c | sort -n | grep "2 " | cut -d" " -f 5-`; do echo "$i"; find . | grep "$i"; echo ""; done
> org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
> org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
> org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
> ./integration/ws/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
> org/jboss/as/test/integration/web/security/SecuredServlet.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
> org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
> org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-12586) Duplicated classes in testsuite, content slightly differs in some cases
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-12586?page=com.atlassian.jira.plugi... ]
Lin Gao updated WFLY-12586:
---------------------------
Description:
+underlined text+There are duplicated classes in testsuite, content slightly differs in some cases
{code}
for i in `find . | grep '.*src.*\.java$' | sed "s,.*src/main/java/,,g" | sed "s,.*src/test/java/,,g" | sort | uniq -c | sort -n | grep "2 " | cut -d" " -f 5-`; do echo "$i"; find . | grep "$i"; echo ""; done
org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
./integration/web/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
./integration/web/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
./integration/ws/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
org/jboss/as/test/integration/web/security/SecuredServlet.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
{code}
was:
There are duplicated classes in testsuite, content slightly differs in some cases
{code}
for i in `find . | grep '.*src.*\.java$' | sed "s,.*src/main/java/,,g" | sed "s,.*src/test/java/,,g" | sort | uniq -c | sort -n | grep "2 " | cut -d" " -f 5-`; do echo "$i"; find . | grep "$i"; echo ""; done
org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
./integration/web/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
./integration/web/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
./integration/ws/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
org/jboss/as/test/integration/web/security/SecuredServlet.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
{code}
> Duplicated classes in testsuite, content slightly differs in some cases
> -----------------------------------------------------------------------
>
> Key: WFLY-12586
> URL: https://issues.redhat.com/browse/WFLY-12586
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Rostislav Svoboda
> Priority: Major
>
> +underlined text+There are duplicated classes in testsuite, content slightly differs in some cases
> {code}
> for i in `find . | grep '.*src.*\.java$' | sed "s,.*src/main/java/,,g" | sed "s,.*src/test/java/,,g" | sort | uniq -c | sort -n | grep "2 " | cut -d" " -f 5-`; do echo "$i"; find . | grep "$i"; echo ""; done
> org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/classloading/war/WebInfLibClass.java
> org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/deployment/deploymentoverlay/DeploymentOverlayTestCase.java
> org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
> ./integration/ws/src/test/java/org/jboss/as/test/integration/ejb/security/EjbSecurityDomainSetup.java
> org/jboss/as/test/integration/web/security/SecuredServlet.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/SecuredServlet.java
> org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebSimpleRoleMappingSecurityDomainSetup.java
> org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
> ./integration/web/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
> ./integration/basic/src/test/java/org/jboss/as/test/integration/web/security/WebTestsSecurityDomainSetup.java
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Yeser Amer edited comment on DROOLS-4994 at 2/4/20 4:13 AM:
------------------------------------------------------------
[~uxdlc] Thank you, both solutions are fine for me. In case of a short description, I prefer the first one, but I afraid it will require a long description, so the second one seems more realistic.
was (Author: yamer):
[~uxdlc] Thank you, both solutions are fine for me. In case of a short description, I prefer the first one.
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: UX, UXTeam, drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Jozef Marko commented on DROOLS-4994:
-------------------------------------
Could we please discuss also the text of the hints here? [~yamer] do you have any proposals?
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: UX, UXTeam, drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ]
Yeser Amer commented on DROOLS-4994:
------------------------------------
[~uxdlc] Thank you, both solutions are fine for me. In case of a short description, I prefer the first one.
> Highlight better that expression and graphical collection editor are different
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4994
> URL: https://issues.redhat.com/browse/DROOLS-4994
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Anna Dupliak
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: UX, UXTeam, drools-tools
> Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png
>
>
> Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698
> We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom.
> Suggested solution:
> - to explain the difference directly in the popup, somewhere close to radio buttons create/define.
> Example:
> [1]
> !Screenshot from 2020-01-17 13-56-02.png|thumbnail!
> [2]
> !Screenshot from 2020-01-17 13-56-10.png|thumbnail!
> How that works now:
> Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?"
> What expression should be to make test pass:
> (2 in ?)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13052) Workaround for MicroProfile Config TCK "ShouldThrowException" failure
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFLY-13052?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFLY-13052:
-------------------------------
Summary: Workaround for MicroProfile Config TCK "ShouldThrowException" failure (was: Workaround MicroProfile Config TCK "ShouldThrowException" failure)
> Workaround for MicroProfile Config TCK "ShouldThrowException" failure
> ---------------------------------------------------------------------
>
> Key: WFLY-13052
> URL: https://issues.redhat.com/browse/WFLY-13052
> Project: WildFly
> Issue Type: Component Upgrade
> Components: MP Config
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
>
> Some MicroProfile Config TCK tests expects deployment failure by annotating the @Deployment with @ShouldThrowException(DeploymentException.class).
> Due to https://issues.redhat.com/browse/WFARQ-59, the deployment exception is not properly handled on the Arquillian client side and the test fails because, the thrown exception is not of the proper type.
> This can be worked around by adding a DeploymentExceptionTransformer that will transform the exception into the proper type.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months