[JBoss JIRA] (WFLY-13304) JwtActivationProcessor throws NPE when LoginConfig#realmName not declared
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13304?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFLY-13304:
------------------------------------
Fix Version/s: 20.0.0.Beta1
> JwtActivationProcessor throws NPE when LoginConfig#realmName not declared
> -------------------------------------------------------------------------
>
> Key: WFLY-13304
> URL: https://issues.redhat.com/browse/WFLY-13304
> Project: WildFly
> Issue Type: Bug
> Components: MP JWT
> Affects Versions: 19.0.0.Final
> Reporter: Michael Edgar
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 20.0.0.Beta1
>
>
> When starting a Microprofile application utilizing the {{org.eclipse.microprofile.auth.LoginConfig}} annotation, a {{NullPointerException}} is thrown if the annotation does not declare the {{realmName}} property.
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) {} MSC000001: Failed to start service jboss.deployment.unit."example.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."example.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "example.war"
> at org.jboss.as.server@11.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.microprofile.jwt-smallrye@19.0.0.Final//org.wildfly.extension.microprofile.jwt.smallrye.JwtActivationProcessor.deploy(JwtActivationProcessor.java:80)
> at org.jboss.as.server@11.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5130) Externalize org.drools.compiler.commons.jci.compilers.NativeJavaCompiler
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5130?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5130:
---------------------------------
Description:
-NativeJavaCompiler is a utility class the may be used by different client code, unrelated to anything drools-specific and by itsel.
Currently it is defined inside the drools-compiler module that, in turns, brings in a series of unneeded dependencies for such class itself.
Moving such class (and the other strictly-needed classes) will make it re-usable without unwanted dependencies.-
Update Drools to support the new module MemoryCompiler as defined here
https://issues.redhat.com/browse/DROOLS-5206
was:
NativeJavaCompiler is a utility class the may be used by different client code, unrelated to anything drools-specific and by itsel.
Currently it is defined inside the drools-compiler module that, in turns, brings in a series of unneeded dependencies for such class itself.
Moving such class (and the other strictly-needed classes) will make it re-usable without unwanted dependencies.
> Externalize org.drools.compiler.commons.jci.compilers.NativeJavaCompiler
> ------------------------------------------------------------------------
>
> Key: DROOLS-5130
> URL: https://issues.redhat.com/browse/DROOLS-5130
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> -NativeJavaCompiler is a utility class the may be used by different client code, unrelated to anything drools-specific and by itsel.
> Currently it is defined inside the drools-compiler module that, in turns, brings in a series of unneeded dependencies for such class itself.
> Moving such class (and the other strictly-needed classes) will make it re-usable without unwanted dependencies.-
> Update Drools to support the new module MemoryCompiler as defined here
> https://issues.redhat.com/browse/DROOLS-5206
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5130) Externalize org.drools.compiler.commons.jci.compilers.NativeJavaCompiler
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5130?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5130:
---------------------------------
Description:
--NativeJavaCompiler is a utility class the may be used by different client code, unrelated to anything drools-specific and by itsel.
Currently it is defined inside the drools-compiler module that, in turns, brings in a series of unneeded dependencies for such class itself.
Moving such class (and the other strictly-needed classes) will make it re-usable without unwanted dependencies.--
Update Drools to support the new module MemoryCompiler as defined here
https://issues.redhat.com/browse/DROOLS-5206
was:
-NativeJavaCompiler is a utility class the may be used by different client code, unrelated to anything drools-specific and by itsel.
Currently it is defined inside the drools-compiler module that, in turns, brings in a series of unneeded dependencies for such class itself.
Moving such class (and the other strictly-needed classes) will make it re-usable without unwanted dependencies.-
Update Drools to support the new module MemoryCompiler as defined here
https://issues.redhat.com/browse/DROOLS-5206
> Externalize org.drools.compiler.commons.jci.compilers.NativeJavaCompiler
> ------------------------------------------------------------------------
>
> Key: DROOLS-5130
> URL: https://issues.redhat.com/browse/DROOLS-5130
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Luca Molteni
> Priority: Major
>
> --NativeJavaCompiler is a utility class the may be used by different client code, unrelated to anything drools-specific and by itsel.
> Currently it is defined inside the drools-compiler module that, in turns, brings in a series of unneeded dependencies for such class itself.
> Moving such class (and the other strictly-needed classes) will make it re-usable without unwanted dependencies.--
> Update Drools to support the new module MemoryCompiler as defined here
> https://issues.redhat.com/browse/DROOLS-5206
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5206) Create a separated module for InMemory Compiler
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5206?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5206:
---------------------------------
Description:
Currently we do in-memory compilation and loading in different places. Soon we'll have it in
- Drools Executable Model
- PMML
- DMN
By creating a new external module that does exactly that (in-memory compile and load it in the class loader) without being coupled to Drools in anyway we can reuse it.
Related to https://issues.redhat.com/browse/DROOLS-5130
was:
Currently we do in-memory compilation and loading in different places. Soon we'll have it in
- Drools Executable Model
- PMML
- DMN
By creating a new external module that does exactly that (in-memory compile and load it in the class loader) without being coupled to Drools in anyway we can reuse it.
> Create a separated module for InMemory Compiler
> -----------------------------------------------
>
> Key: DROOLS-5206
> URL: https://issues.redhat.com/browse/DROOLS-5206
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> Currently we do in-memory compilation and loading in different places. Soon we'll have it in
> - Drools Executable Model
> - PMML
> - DMN
> By creating a new external module that does exactly that (in-memory compile and load it in the class loader) without being coupled to Drools in anyway we can reuse it.
> Related to https://issues.redhat.com/browse/DROOLS-5130
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5206) Create a separated module for InMemory Compiler
by Luca Molteni (Jira)
Luca Molteni created DROOLS-5206:
------------------------------------
Summary: Create a separated module for InMemory Compiler
Key: DROOLS-5206
URL: https://issues.redhat.com/browse/DROOLS-5206
Project: Drools
Issue Type: Enhancement
Components: core engine
Reporter: Luca Molteni
Assignee: Luca Molteni
Currently we do in-memory compilation and loading in different places. Soon we'll have it in
- Drools Executable Model
- PMML
- DMN
By creating a new external module that does exactly that (in-memory compile and load it in the class loader) without being coupled to Drools in anyway we can reuse it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5205) Behavioural updates
by Toshiya Kobayashi (Jira)
Toshiya Kobayashi created DROOLS-5205:
-----------------------------------------
Summary: Behavioural updates
Key: DROOLS-5205
URL: https://issues.redhat.com/browse/DROOLS-5205
Project: Drools
Issue Type: Feature Request
Components: core engine
Reporter: Toshiya Kobayashi
Assignee: Toshiya Kobayashi
Allow users to implement compensation actions in case of unexpected unMatch/reMatch (especially, related to incremental compilation. See DROOLS-5028)
Some ideas:
A) ActivationUnMatchListener
https://issues.redhat.com/browse/JBRULES-3144
B) Allow annotation on rule (or unit) that says @RefireOnChange(LHS, RHS) // can be one or the other, or both.
C) Rising/Falling edges
http://blog.athico.com/2010/05/drools-language-enhancements-drools-6.html
"was not true, is true" "was true, still true", " was true, not true now"
people should actually be able to do this a special node in the rete graph.
it can be combined with branching too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years