[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service
by Daniele Zonca (Jira)
Daniele Zonca created DROOLS-4161:
-------------------------------------
Summary: Scenario Test: UX for DMN Decision service
Key: DROOLS-4161
URL: https://issues.jboss.org/browse/DROOLS-4161
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Daniele Zonca
Assignee: Tao Zhu
As user I want to test my decision service from a DMN model.
User needs to specify DMN model and decision service name to be tested.
Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4516) The expression for secret value under server-identities in test-security-realm does not work .
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFCORE-4516?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFCORE-4516:
-------------------------------------
Component/s: Management
(was: Remoting)
> The expression for secret value under server-identities in test-security-realm does not work .
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-4516
> URL: https://issues.jboss.org/browse/WFCORE-4516
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Reporter: Indrajit Ingawale
> Assignee: Flavia Rainone
> Priority: Major
>
> The expression for secret value under server-identities in test-security-realm does not work , even though it shows "expressions-allowed" to true like below .
> ----------------------------
> [standalone@localhost:9990 /] /core-service=management/security-realm=test-security-realm/server-identity=secret:read-resource-description()
> {
> "outcome" => "success",
> .
> .
> "attributes" =>
> {. . . . . }
> ,
> "value" =>
> { "type" => STRING, "description" => "The secret / password - Base64 Encoded.", "expressions-allowed" => true, "required" => true, "nillable" => true, "alternatives" => ["credential-reference"], "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {}
> }
> }
> ----------------------------
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4516) The expression for secret value under server-identities in test-security-realm does not work .
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFCORE-4516?page=com.atlassian.jira.plugi... ]
Darran Lofthouse reassigned WFCORE-4516:
----------------------------------------
Assignee: Darran Lofthouse (was: Flavia Rainone)
> The expression for secret value under server-identities in test-security-realm does not work .
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-4516
> URL: https://issues.jboss.org/browse/WFCORE-4516
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Reporter: Indrajit Ingawale
> Assignee: Darran Lofthouse
> Priority: Major
>
> The expression for secret value under server-identities in test-security-realm does not work , even though it shows "expressions-allowed" to true like below .
> ----------------------------
> [standalone@localhost:9990 /] /core-service=management/security-realm=test-security-realm/server-identity=secret:read-resource-description()
> {
> "outcome" => "success",
> .
> .
> "attributes" =>
> {. . . . . }
> ,
> "value" =>
> { "type" => STRING, "description" => "The secret / password - Base64 Encoded.", "expressions-allowed" => true, "required" => true, "nillable" => true, "alternatives" => ["credential-reference"], "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {}
> }
> }
> ----------------------------
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4517) Restore adding the java.se module in the launcher API
by James Perkins (Jira)
James Perkins created WFCORE-4517:
-------------------------------------
Summary: Restore adding the java.se module in the launcher API
Key: WFCORE-4517
URL: https://issues.jboss.org/browse/WFCORE-4517
Project: WildFly Core
Issue Type: Bug
Components: Launcher
Reporter: James Perkins
Assignee: James Perkins
In WFCORE-4415 the {{--add-modules=java.se}} was removed from the launcher API. The fix for MODULES-372 was included in the jboss-modules 1.9.1.Final upgrade. However the launcher is designed to work with older versions of WildFly as well as the current version. Therefore the {{java.se}} module should automatically be added in order to work with older versions of WildFly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12182) Resolve failure with EAP 7.2 mixed domain tests on JDK 12
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12182?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-12182:
---------------------------------------
Assignee: James Perkins (was: Yeray Borges)
> Resolve failure with EAP 7.2 mixed domain tests on JDK 12
> ---------------------------------------------------------
>
> Key: WFLY-12182
> URL: https://issues.jboss.org/browse/WFLY-12182
> Project: WildFly
> Issue Type: Task
> Components: Management, Test Suite
> Reporter: Brian Stansberry
> Assignee: James Perkins
> Priority: Major
>
> The EAP 7.2 mixed domain tests have been failing with JDK 12 since May 1. Task is to figure out why.
> The changes that went into master before the first failure are here:
> https://ci.wildfly.org/viewLog.html?buildId=148651&buildTypeId=WF_MasterL...
> Note this includes a WildFly Core upgrade, so that could include all sorts of things.
> The mixed domain runs report 12 failures, but the non-EAP 7.2 ones looks to be just because the 7.2 problems mess up the test env state, breaking later tests. This is something we've always seen.
> The failure occurs when starting the legacy Process Controller:
> {code}
> [0m05:12:02,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final-redhat-00001
> [0m[33m05:12:02,692 WARN [org.jboss.modules.define] (main) Failed to define class org.jboss.logging.MDC in Module "org.jboss.logging" version 3.3.2.Final-redhat-00001 from local module loader @2ddc9a9f (finder: local module finder @298a5e20 (roots: /store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/domains/MixedDomain720TestSuite/slave/added-modules,/store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/domains/MixedDomain720TestSuite/added-modules,/store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/old-versions/jboss-eap-7.2.0/modules,/store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/old-versions/jboss-eap-7.2.0/modules/system/layers/base)): org.jboss.modules.ModuleLoadError: java.se
> at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74)
> at org.jboss.modules.Module.getPathsUnchecked(Module.java:1608)
> at org.jboss.modules.Module.loadModuleClass(Module.java:726)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:423)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:519)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126)
> at org.jboss.modules.Module.loadModuleClass(Module.java:731)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.start(Main.java:80)
> at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.main(Main.java:76)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> [0mException in thread "main" org.jboss.modules.ModuleLoadError: java.se
> at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74)
> at org.jboss.modules.Module.getPathsUnchecked(Module.java:1608)
> at org.jboss.modules.Module.loadModuleClass(Module.java:726)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:423)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:519)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126)
> at org.jboss.modules.Module.loadModuleClass(Module.java:731)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.start(Main.java:80)
> at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.main(Main.java:76)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> {code}
> I'm labeling this a Task for now rather than a Bug because I suspect the problem may be in the test infrastructure. In particular I recommend having a look at anything that changed in the WF Core launcher module in the 9.0.0.Beta4 release. The mixed domain tests use DomainLifecycleUtil, which in turn uses launcher's DomainCommandBuilder. Those use java.lang.Process to start a legacy PC using the JDK 11 jvm on the CI server. So the PC process is completely separate from the test client or the master PC/HC/servers. No reason the old code should stop working with JDK 11 so I suspect something has changed with the launcher.
> [~jamezp] [~ropalka] FYI
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4137) KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build
by Justin Holmes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4137?page=com.atlassian.jira.plugi... ]
Justin Holmes commented on DROOLS-4137:
---------------------------------------
Yes it is. We are working to provide a version without our intellectual property, and will let you know when that is complete. We appreciate your collaboration here.
> KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-4137
> URL: https://issues.jboss.org/browse/DROOLS-4137
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.22.0.Final
> Reporter: Justin Holmes
> Assignee: Mario Fusco
> Priority: Major
>
> I would like to have kie-maven-plugin build the KJar with a serialized KieBase so that it takes less time to boot strap drools. It appears that the maven configuration used by the kie-maven-plugin is broken, or at least there is not sufficient documentation to set it up.
> See https://groups.google.com/forum/#!topic/drools-setup/0TZvE5lpcto for more information.
> Documentation is VERY limited / scattered in different areas. It probably needs updates. If we can get help to get the build working / bug fixed, we would be happy to submit a doc fix.
> We are trying to use drools in a severless environment (though not quite ready for Quarkus). If we are unable to use this build feature, we may be unable to use drools.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month