[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5955:
--------------------------------
Sprint: 2021 Week 04-06 (from Jan 25)
> KieScanner not properly updating model assets (classes) on incremental updates
> ------------------------------------------------------------------------------
>
> Key: DROOLS-5955
> URL: https://issues.redhat.com/browse/DROOLS-5955
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.48.0.Final
> Reporter: B Brown
> Assignee: Mario Fusco
> Priority: Major
> Attachments: LogFile.txt, RunTest.java, TestScannerUpdate-1.0.0-SNAPSHOT.jar
>
>
> KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
> Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
> It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce".
> This was using 7.48.Final drools libraries and Business Central 7.48.Final but experienced similar issue before on 7.43.1.Final as well.
> I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file.
>
> My dependencies in maven for RunTest.java were:
> * group: org.drools artifact: drools-bom ,version: 7.48.Final
> * group: org.kie artifact: kie-ci
> * group: org.drools artifact: drools-workbench-models-guided-dtable
> * group: org.drools artifact: drools-workbench-models-guided-template
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months
[Red Hat JIRA] (LOGMGR-283) The TCCL should be set when configuring resources
by James Perkins (Jira)
James Perkins created LOGMGR-283:
------------------------------------
Summary: The TCCL should be set when configuring resources
Key: LOGMGR-283
URL: https://issues.redhat.com/browse/LOGMGR-283
Project: JBoss Log Manager
Issue Type: Bug
Reporter: James Perkins
Assignee: James Perkins
When configuring resources the TCCL should be set to the class loader for the type being configured. In the case of a modular environment the type may use the TCCL to initialize other types. For example in WildFly if a {{custom-handler}} is used that handler may be in it's own module and attempt to use the TCCL to initialize another type.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months
[Red Hat JIRA] (WFLY-10863) MP Health is not available in domain mode
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFLY-10863?page=com.atlassian.jira.plugi... ]
Jeff Mesnil reassigned WFLY-10863:
----------------------------------
Assignee: Martin Stefanko (was: Jeff Mesnil)
> MP Health is not available in domain mode
> -----------------------------------------
>
> Key: WFLY-10863
> URL: https://issues.redhat.com/browse/WFLY-10863
> Project: WildFly
> Issue Type: Feature Request
> Components: MP Health
> Reporter: Rostislav Svoboda
> Assignee: Martin Stefanko
> Priority: Major
> Labels: domain-mode
>
> MP Health is not available in domain mode.
> Analysis is not saying that domain is out of scope, EAP7 RFE is not explicit about this either.
> We may resolve this just by making it explicit, that MP health is just fo standalone for now.
> For domain we should at least have a plan what to do and how
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months