[JBoss JIRA] (WFCORE-3885) CLI script prints WARNING with JDK10+ if CLI connects to server
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3885?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-3885:
----------------------------------------------
[~mkopecky], I used JDK 10, no more warning. Aesh relies on sun.misc.Signal that is still accessible in JDK 10, and there are no replacement API yet. So this one is the only warning impacting the CLI. CLI running with --illegal-access=deny worked just fine.
> CLI script prints WARNING with JDK10+ if CLI connects to server
> ---------------------------------------------------------------
>
> Key: WFCORE-3885
> URL: https://issues.jboss.org/browse/WFCORE-3885
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Scripts
> Reporter: Marek Kopecký
> Assignee: Jean-Francois Denise
> Priority: Blocker
>
> CLI prints WARNING with JDK10+ if CLI connects to server
> {noformat}
> [mkopecky@dhcp-10-40-5-52 bin]$ java -version
> java version "10" 2018-03-20
> Java(TM) SE Runtime Environment 18.3 (build 10+46)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10+46, mixed mode)
> [mkopecky@dhcp-10-40-5-52 bin]$ ./jboss-cli.sh "echo test"
> test
> [mkopecky@dhcp-10-40-5-52 bin]$ ./jboss-cli.sh -c "echo test"
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.xnio.nio.NioXnio$2 (jar:file:/home/mkopecky/playground/eap/7.2.0.CD13.1/jboss-eap-7.2/modules/system/layers/base/org/jboss/xnio/nio/main/xnio-nio-3.6.3.Final.jar!/) to constructor sun.nio.ch.EPollSelectorProvider()
> WARNING: Please consider reporting this to the maintainers of org.xnio.nio.NioXnio$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> test
> [mkopecky@dhcp-10-40-5-52 bin]$
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10446) Attach names associated with a deployment to DeploymentUnit
by Peter Palaga (JIRA)
Peter Palaga created WFLY-10446:
-----------------------------------
Summary: Attach names associated with a deployment to DeploymentUnit
Key: WFLY-10446
URL: https://issues.jboss.org/browse/WFLY-10446
Project: WildFly
Issue Type: Task
Components: Web (Undertow)
Reporter: Peter Palaga
Assignee: Peter Palaga
To be able to secure Camel CXF endpoints in WildFly Camel, we need an access to DeploymentInfo produced by UndertowDeploymentInfoService. Currently, the service name of UndertowDeploymentInfoService is assembled out of several parts including server name, host name and deployment name. These three are defined by a complex logic that checks various sources and defaults. So, rather than copying that logic to WildFly Camel, we'd like to pack those names into a data object and attach it to the deploymentUnit so that it is available to our DeploymentProcessor.
A PR follows.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2587) Java 8 and Drools 7.5.0
by Gibran Castillo (JIRA)
Gibran Castillo created DROOLS-2587:
---------------------------------------
Summary: Java 8 and Drools 7.5.0
Key: DROOLS-2587
URL: https://issues.jboss.org/browse/DROOLS-2587
Project: Drools
Issue Type: Bug
Components: decision tables
Affects Versions: 7.5.0.Final
Environment: Development
Reporter: Gibran Castillo
Assignee: Mario Fusco
I upgraded my Drools 5.x (drools-compiler 5.2.1.Final, drools-decisiontables 5.4.0.Final, and drools-templates 5.4.0.Final; jbpm-flow 5.1.1.Final, jbpm-bmpn2 5.1.1.Final and with their respective dependencies) Java 1.7.0_21 job to drools 7.5.0 and use kie-api/kie-ci and Java 1.8.0_162; I had to do some refactoring because now drools is part of the KIE (Knowledge Is Everything) umbrella, specifically the code below:
KieServices ks = KieServices.Factory.get();
KieContainer kc = ks.getKieClasspathContainer();
KieSession ks = kc.newKieSession("ksession-dtables"); //stateful session
FactHandle fh = ks.insert(fact);
ks.fireAllRules();
....
I added the pom.properties file and kmodule.xml file. The java job builds successfully. When I run the java job the packages and rules are loaded into the Knowledge Base but only the first rules fire up and then it stops or ends.
This seems to be a bug in the decision table (spreadsheet), it works with Java 7/Drools 5 but not with Java 8/Drools 7
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month