You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Zineb BENDHIBA (Jira)" <ji...@apache.org> on 2020/09/15 07:37:00 UTC
[jira] [Updated] (CAMEL-15531) Optaplanner - Upgrade component with
usage of SolverManager
[ https://issues.apache.org/jira/browse/CAMEL-15531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zineb BENDHIBA updated CAMEL-15531:
-----------------------------------
Description:
This upgrade of code is needed to use optaplanner-quarkus extension, and also for users not using config file anymore.
SolverManager can be used easily with spring boot and quarkus. The SolverConfig will be automatically generated. no need in camel to generate a Solver from a config file ==> Usage of SolverManager and SolverJob.
was:
This upgrade of code is needed to use optaplanner-quarkus, and also for users not using config file anymore.
In Quarkus, the SolverConfig will be automatically generated, and if a config file exists, it's taken in consideration ==> no need in camel to generate a Solver and all its cats again on camel ==> Usage of SolverManager
> Optaplanner - Upgrade component with usage of SolverManager
> -----------------------------------------------------------
>
> Key: CAMEL-15531
> URL: https://issues.apache.org/jira/browse/CAMEL-15531
> Project: Camel
> Issue Type: New Feature
> Components: camel-optaplanner
> Affects Versions: 3.6.0
> Reporter: Zineb BENDHIBA
> Assignee: Zineb BENDHIBA
> Priority: Minor
>
> This upgrade of code is needed to use optaplanner-quarkus extension, and also for users not using config file anymore.
> SolverManager can be used easily with spring boot and quarkus. The SolverConfig will be automatically generated. no need in camel to generate a Solver from a config file ==> Usage of SolverManager and SolverJob.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)