[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Description:
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
was:
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".
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
> 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] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Description:
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".
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
was:
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".
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 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
> 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".
>
> 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] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Description:
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".
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 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
was:
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". I've also attached the final kjar that caused the error, the main method that ran the test as well as the log file.
> 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".
>
> 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 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] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Attachment: RunTest.java
> 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". I've also attached the final kjar that caused the error, the main method that ran the test as well as the log file.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months
[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Attachment: TestScannerUpdate-1.0.0-SNAPSHOT.jar
> 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". I've also attached the final kjar that caused the error, the main method that ran the test as well as the log file.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months
[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Attachment: LogFile.txt
> 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". I've also attached the final kjar that caused the error, the main method that ran the test as well as the log file.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months
[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
B Brown created DROOLS-5955:
-------------------------------
Summary: 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
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". I've also attached the final kjar that caused the error, the main method that ran the test as well as the log file.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months
[Red Hat JIRA] (WFLY-14310) JPASubsystemAdd uses non-standard attribute value resolution
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-14310:
---------------------------------------
Summary: JPASubsystemAdd uses non-standard attribute value resolution
Key: WFLY-14310
URL: https://issues.redhat.com/browse/WFLY-14310
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Reporter: Brian Stansberry
Assignee: Brian Stansberry
JPASubsystemAdd processes a couple attributes in non-standard ways, not using AttributeDefinition.resolveModelAttribute. The code handles the primary things resolveModelAttribute handles (default values and basic expression resolution) but it doesn't handle the full set of expression resolution capability WildFly supports.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months