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 7F729200CFD for ; Wed, 6 Sep 2017 16:57:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7E242161C20; Wed, 6 Sep 2017 14:57:07 +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 CF25616171A for ; Wed, 6 Sep 2017 16:57:06 +0200 (CEST) Received: (qmail 70292 invoked by uid 500); 6 Sep 2017 14:57:04 -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 70283 invoked by uid 99); 6 Sep 2017 14:57:04 -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, 06 Sep 2017 14:57:04 +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 45A3D18A7C0 for ; Wed, 6 Sep 2017 14:57:04 +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 FoMLXSXLyUNb for ; Wed, 6 Sep 2017 14:57:03 +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 E19AD60EF3 for ; Wed, 6 Sep 2017 14:57: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 F2A79E0ECA for ; Wed, 6 Sep 2017 14:57: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 4289424157 for ; Wed, 6 Sep 2017 14:57:00 +0000 (UTC) Date: Wed, 6 Sep 2017 14:57:00 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CAMEL-11752) camel-spring-boot : improve handling classic spring xml with spring-boot MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 06 Sep 2017 14:57:07 -0000 [ https://issues.apache.org/jira/browse/CAMEL-11752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155480#comment-16155480 ] Claus Ibsen commented on CAMEL-11752: ------------------------------------- Okay its a bit tricky as when XML parser creates a new CamelContextFactoryBean then its in creation of a CamelContext already. So if you ask spring to create a bean of CamelContext (eg spring boot auto configuration) then it goes back into the factory bean. > camel-spring-boot : improve handling classic spring xml with spring-boot > -------------------------------------------------------------------------- > > Key: CAMEL-11752 > URL: https://issues.apache.org/jira/browse/CAMEL-11752 > Project: Camel > Issue Type: Improvement > Components: camel-spring, camel-spring-boot > Reporter: Luca Burgazzoli > Assignee: Claus Ibsen > Fix For: 2.20.0 > > > Within a spring-boot based application it is possible to load spring xml based camel context but that's may cause issues as spring boot won't create and configure a camel context but it will be created by the camel-spring based on the xml file so any context configuration one may expect to tweak via spring-boot properties won't be taken into account. > An example can be found here: https://github.com/lburgazzoli/camel-spring-xml were as example, the set the camel context name with the property camel.springboot.name does not work but the camel context will be named according to the spring-xml file. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)