Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 10C7A200D18 for ; Wed, 11 Oct 2017 09:30:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0F0341609E4; Wed, 11 Oct 2017 07:30:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 543561609CA for ; Wed, 11 Oct 2017 09:30:04 +0200 (CEST) Received: (qmail 88046 invoked by uid 500); 11 Oct 2017 07:30:03 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 88037 invoked by uid 99); 11 Oct 2017 07:30:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2017 07:30:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id BAB9218418F for ; Wed, 11 Oct 2017 07:30:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id wFXvqnzRv9me for ; Wed, 11 Oct 2017 07:30:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3C42F5F19C for ; Wed, 11 Oct 2017 07:30:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6ACDFE0631 for ; Wed, 11 Oct 2017 07:30:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2611324386 for ; Wed, 11 Oct 2017 07:30:00 +0000 (UTC) Date: Wed, 11 Oct 2017 07:30:00 +0000 (UTC) From: "Thomas Diesler (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CAMEL-11889) Kie assumes that the TCCL can load its services MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 11 Oct 2017 07:30:05 -0000 [ https://issues.apache.org/jira/browse/CAMEL-11889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199909#comment-16199909 ] Thomas Diesler commented on CAMEL-11889: ---------------------------------------- The PR is working, but I haven't decided yet whether the correct classloader to use should be that of the Optaplaner component, the Kie API or even that of the user deployment. Kie caches classloaders that are associated with an arbitrary thread. This is of course highly problematic in a modular environment, where the same instance of Kie may be used by multiple modules and even multiple deployments. Only if, that what is cached is part of some static configuration (i.e. independent of deployment content) it can (reluctantly) be done at all. I'll revisit this at my leisure and for now agree with you, that it is not critical. > Kie assumes that the TCCL can load its 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)