You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Dmitry Volodin (JIRA)" <ji...@apache.org> on 2017/10/09 13:16:00 UTC
[jira] [Commented] (CAMEL-11889) OptaPlanner incorrectly assumes
that the TCCL can load kie services
[ https://issues.apache.org/jira/browse/CAMEL-11889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196931#comment-16196931 ]
Dmitry Volodin commented on CAMEL-11889:
----------------------------------------
from component code it uses classloader from Camel context and the problem can occurs on kie level
SolverFactory.createFromXmlResource(configuration.getConfigFile(), getCamelContext().getApplicationContextClassLoader());
> OptaPlanner incorrectly assumes that the TCCL can load kie services
> -------------------------------------------------------------------
>
> Key: CAMEL-11889
> URL: https://issues.apache.org/jira/browse/CAMEL-11889
> Project: Camel
> Issue Type: Bug
> Components: camel-optaplanner
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 2.20.1, 2.21.0
>
>
> The recent update of optaplanner comes with kit-7.3.0.final, which relies on the TCCL
> https://github.com/kiegroup/droolsjbpm-knowledge/blob/7.3.0.Final/kie-api/src/main/java/org/kie/api/internal/utils/ServiceDiscoveryImpl.java#L163
> Perhaps, this can be fixed at the camel-optaplanner component level.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)