[Red Hat JIRA] (DROOLS-5867) Update ApplyPmmlModelCommand to manage both PMML implementations
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5867?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-5867:
-------------------------------------
Description:
Currently, ApplyPmmlModelCommand (inside drools) invoke directly the legacy PMML delegate (ApplyPmmlModelCommandExecutorImpl).
# define PMMLCommandExecutor interface inside kie-internal (droolsjbpm-knowledge)
# write a PMMLCommandExecutor factory (where ? It must be visible by drools-core inside ApplyPmmlModelCommand)
# write a PMMLCommandExecutor implementation (where ? It must be visible by PMMLCommandExecutor factory )
# modify ApplyPmmlModelCommand to switch between factories/implementations.
was:
Currently, ApplyPmmlModelCommand (inside drools) invoke directly the legacy PMML delegate (ApplyPmmlModelCommandExecutorImpl).
# code a PMML-trusty implementation of ApplyPmmlModelCommandExecutor (needed ?)
# modify ApplyPmmlModelCommand to switch between implementations.
> Update ApplyPmmlModelCommand to manage both PMML implementations
> -----------------------------------------------------------------
>
> Key: DROOLS-5867
> URL: https://issues.redhat.com/browse/DROOLS-5867
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: TrustyAI
>
> Currently, ApplyPmmlModelCommand (inside drools) invoke directly the legacy PMML delegate (ApplyPmmlModelCommandExecutorImpl).
> # define PMMLCommandExecutor interface inside kie-internal (droolsjbpm-knowledge)
> # write a PMMLCommandExecutor factory (where ? It must be visible by drools-core inside ApplyPmmlModelCommand)
> # write a PMMLCommandExecutor implementation (where ? It must be visible by PMMLCommandExecutor factory )
> # modify ApplyPmmlModelCommand to switch between factories/implementations.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (DROOLS-4606) DMN alpha network POC
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4606?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4606:
-----------------------------------
Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 46-48 (from Nov 9))
> DMN alpha network POC
> ---------------------
>
> Key: DROOLS-4606
> URL: https://issues.redhat.com/browse/DROOLS-4606
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Luca Molteni
> Priority: Major
>
> Start refactoring work to support alpha network
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14143) Can not inject bean from module
by Mariusz Kulig (Jira)
Mariusz Kulig created WFLY-14143:
------------------------------------
Summary: Can not inject bean from module
Key: WFLY-14143
URL: https://issues.redhat.com/browse/WFLY-14143
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, Class Loading
Affects Versions: 21.0.1.Final
Reporter: Mariusz Kulig
Assignee: Matěj Novotný
Attachments: mymodule.zip, reproduce_sample.zip
Bean from module cannot be injected to bean in deployment. It works properly on Wildfly 20.0.1.Final but does not work on Wildlfy 21.0.1.Final.
I registered module which contains @ApplicationScoped CDI bean. I tried do deploy WAR archive that contains library that depends on this module. The library contains proper entry in Dependencies section in MANIFEST.MF file.
I get exception:
{code:java}
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type HelloService with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject com.example.mylib.MyLib.helloService
at com.example.mylib.MyLib.helloService(MyLib.java:0)
at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14136) Activate MP Rest Client TCK with -Dts.ee9 profile; resolve failures
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14136?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-14136:
------------------------------------
Labels: EE9 (was: )
> Activate MP Rest Client TCK with -Dts.ee9 profile; resolve failures
> -------------------------------------------------------------------
>
> Key: WFLY-14136
> URL: https://issues.redhat.com/browse/WFLY-14136
> Project: WildFly
> Issue Type: Task
> Components: MP REST Client
> Reporter: Brian Stansberry
> Assignee: Alessio Soldano
> Priority: Major
> Labels: EE9
>
> When the ee-9 modules were added I thought I had enabled the MP Rest Client TCK when the -Dts.ee9 profile was executed. It turns out I had not. The profile does the various set up work but the default-test surefire execution was not enabled, so the tests aren't actually run. I discovered this when working on WFLY-14049.
> I believe 16 test will fail if it is enabled, so part of this task is to sort out what that's about.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (DROOLS-5124) SceSim editor is not recognizing "default" session in kmodule
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5124?page=com.atlassian.jira.plug... ]
Matteo Mortari commented on DROOLS-5124:
----------------------------------------
As of today, sanity check for 7.47.0.Final, the behaviour is still the same as originally reported.
> SceSim editor is not recognizing "default" session in kmodule
> -------------------------------------------------------------
>
> Key: DROOLS-5124
> URL: https://issues.redhat.com/browse/DROOLS-5124
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Matteo Mortari
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot 2020-03-03 at 15.49.48.png, Screenshot 2020-03-03 at 15.51.52.png
>
>
> steps to reproduce.
> Similaely to sanity check procedure "Test native (DRL) decision services".
> Requires defining in kmodule of the BC Project a default kiebase/kiesession to use it later in the step to invoke on Kie Server.
> So one would normally create something like this in the Project kmodule
> !Screenshot 2020-03-03 at 15.49.48.png|thumbnail!
> But later the scesim editor is not picking up the default:
> !Screenshot 2020-03-03 at 15.51.52.png|thumbnail!
> so it would fail with the error for non-exiting null kie session:
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months