[JBoss JIRA] (DROOLS-845) @KSession throws exception when using kmodule in separate jar
by José Filipe Neis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-845?page=com.atlassian.jira.plugin... ]
José Filipe Neis edited comment on DROOLS-845 at 8/11/17 3:03 PM:
------------------------------------------------------------------
Checked the source code and the problem is happening because AnnotationsPostProcessor assumes there is always a ReleaseId specified.
Just created a [pull request|https://github.com/kiegroup/droolsjbpm-integration/pull/1127] for 7.2.x.
was (Author: jfneis):
Checked the source code and the problem is happening because AnnotationsPostProcessor assumes there is always a ReleaseId specified.
Just created a [pull request|AnnotationsPostProcessor] for 7.2.x.
> @KSession throws exception when using kmodule in separate jar
> -------------------------------------------------------------
>
> Key: DROOLS-845
> URL: https://issues.jboss.org/browse/DROOLS-845
> Project: Drools
> Issue Type: Bug
> Components: core engine, decision tables, kie server
> Affects Versions: 6.2.0.Final
> Environment: windows 7
> Reporter: lucio piccoli
> Assignee: Mario Fusco
> Attachments: drools-bug.zip
>
>
> i am using drools with a kmodules.xml and decisiontable inside a separate jar file. when i attempt to bind the @KSession to the spring application context it throws an nullpointer exception deep inside the annotation.
> org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'oft.onlineservice.business.FeeRulesEngineTest': Injection of kie dependencies failed; nested exception is java.lang.NullPointerException
> at org.kie.spring.annotations.AnnotationsPostProcessor.postProcessPropertyValues(AnnotationsPostProcessor.java:109)
> using a simple junittest shows the problem.
> public class FeeRulesEngineTest {
> @KSession( "ksession1")
> private StatelessKieSession ksession;
> @KBase("feeDecisionTable")
> private KieBase kbase;
> the kmodule.xml
> <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
> <kbase name="feeDecisionTable" packages="oft.rulesengine" default="true">
> <ksession name="ksession1" type="stateless" default="true" >
> </ksession>
> </kbase>
> </kmodule>
> the spring config is using the annonation postprocessor.
> <kie:import />
> <bean id="kiePostProcessor"
> class="org.kie.spring.annotations.KModuleAnnotationPostProcessor"/>
>
> my curent work around to is to use @Autowire for the KSession and KBase.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (LOGMGR-169) An invalid path for offline CLI fails with a confusing error
by James Perkins (JIRA)
James Perkins created LOGMGR-169:
------------------------------------
Summary: An invalid path for offline CLI fails with a confusing error
Key: LOGMGR-169
URL: https://issues.jboss.org/browse/LOGMGR-169
Project: JBoss Log Manager
Issue Type: Bug
Reporter: James Perkins
Assignee: James Perkins
If the {{jboss-home}} configuration property is not set the following error message is not very informative.
{code}
Execution default-cli of goal org.wildfly.plugins:wildfly-maven-plugin:1.2.0.Beta1:execute-commands failed: WFLYLNCHR0001: The path 'null' does not exist
{code}
A better validation message should be printed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-3003) Elytron subsystem fails to boot if SecurityProvider cannot be loaded.
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3003?page=com.atlassian.jira.plugi... ]
Ingo Weiss updated WFCORE-3003:
-------------------------------
Labels: jdk9 (was: )
> Elytron subsystem fails to boot if SecurityProvider cannot be loaded.
> ---------------------------------------------------------------------
>
> Key: WFCORE-3003
> URL: https://issues.jboss.org/browse/WFCORE-3003
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Tomaz Cerar
> Labels: jdk9
>
> Trying to run secmgr testsuite under JDK9 results in
> {noformat}
> Caused by: java.util.ServiceConfigurationError: java.security.Provider: Provider com.sun.deploy.security.MozillaJSSProvider could not be instantiated
> at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:581)
> at java.base/java.util.ServiceLoader.access$100(ServiceLoader.java:390)
> at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:799)
> at java.base/java.util.ServiceLoader$ProviderImpl.get(ServiceLoader.java:721)
> at java.base/java.util.ServiceLoader$3.next(ServiceLoader.java:1389)
> at java.base/java.lang.Iterable.forEach(Iterable.java:74)
> at org.wildfly.extension.elytron//org.wildfly.extension.elytron.ProviderDefinitions$1$1.get(ProviderDefinitions.java:201)
> at org.wildfly.extension.elytron//org.wildfly.extension.elytron.ProviderDefinitions$1$1.get(ProviderDefinitions.java:158)
> at org.wildfly.extension.elytron//org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc//org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> {noformat}
> and server doesn't start.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9220) Upgrade Apache Commons Lang to 3.6
by Stoyan Petrov (JIRA)
[ https://issues.jboss.org/browse/WFLY-9220?page=com.atlassian.jira.plugin.... ]
Stoyan Petrov commented on WFLY-9220:
-------------------------------------
Agree, commons-lang3 is not backward compatible with commons-lang2
but it seems a lot of new libraries use new one, package is different: org.apache.commons.lang3
Example of "common" error: java.lang.ClassNotFoundException: org.apache.commons.lang3.StringUtils
It seems only definition of both libs solve the problem. But if there is not such core lib in WFLY then this is not mandatory.
> Upgrade Apache Commons Lang to 3.6
> ----------------------------------
>
> Key: WFLY-9220
> URL: https://issues.jboss.org/browse/WFLY-9220
> Project: WildFly
> Issue Type: Component Upgrade
> Environment: wildfly-11.0.0.Beta1
> Reporter: Stoyan Petrov
> Assignee: Jason Greene
> Priority: Trivial
>
> Upgrade Apache Commons Lang to 3.6 (from 2.6)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9220) Upgrade Apache Commons Lang to 3.6
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9220?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-9220:
-----------------------------------
why? commons-lang is internal only dependency of CXF that is used by webservices stack.
commons-lang3 is not backward compatible with commons-lang, so upgrading it is not really an option until components that need it, upgrade to new version.
> Upgrade Apache Commons Lang to 3.6
> ----------------------------------
>
> Key: WFLY-9220
> URL: https://issues.jboss.org/browse/WFLY-9220
> Project: WildFly
> Issue Type: Component Upgrade
> Environment: wildfly-11.0.0.Beta1
> Reporter: Stoyan Petrov
> Assignee: Jason Greene
> Priority: Trivial
>
> Upgrade Apache Commons Lang to 3.6 (from 2.6)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8371) Undertow https-listener attributes need marking as alternatives to ssl-context attribute.
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-8371?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-8371:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> Undertow https-listener attributes need marking as alternatives to ssl-context attribute.
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-8371
> URL: https://issues.jboss.org/browse/WFLY-8371
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 11.0.0.Alpha1
>
>
> https-listener with set ssl-context
> {noformat}
> <https-listener name="https" socket-binding="https" ssl-context="serverSSLContext" verify-client="REQUIRED"/>
> {noformat}
> is not verifying client
> {noformat}
> verify-client="REQUIRED"
> {noformat}
> Request
> {noformat}
> curl https://192.168.122.196:8847/ -k
> {noformat}
> should be rejected, but isn't
> {noformat}
> $ curl https://192.168.122.196:8847/ -k
> <!DOCTYPE html>
> <html>
> <head>
> <title>JBoss EAP 7</title>
> <!-- proper charset -->
> <meta http-equiv="content-type" content="text/html;charset=utf-8" />
> <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
> <link rel="stylesheet" type="text/css" href="eap.css" />
> <link rel="shortcut icon" href="favicon.ico" />
> </head>
> <body>
> <div id="container" style="position: absolute; left: 0px; top: 0px; right: 0px; bottom: 0px;">
>
> <!-- header -->
> <div class="header-panel">
> <div class="header-line"> </div>
> <div class="header-top">
> <img class="prod-title" src="images/product_title.png"/><span class="prod-version">7</span>
> </div>
> <div class="header-bottom"> </div>
> </div>
>
>
> <!-- main content -->
> <div id="content">
> <div class="section">
> <h1>Welcome to JBoss EAP 7</h1>
> <h3>Your Red Hat JBoss Enterprise Application Platform is running.</h3>
> <p>
> <a href="/console">Administration Console</a> |
> <a href="https://access.redhat.com/documentation/en/jboss-enterprise-application-p...">Documentation</a> |
> <a href="https://access.redhat.com/discussions">Online User Groups</a> <br/>
> </p>
> <sub>To replace this page simply deploy your own war with / as its context path.<br/>
> To disable it, remove the "welcome-content" handler for location / in the undertow subsystem.</sub>
> </div>
> </div>
> <div id="footer"> </div>
> </div>
> </body >
> </html>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months