Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 6 May 2011 13:02:03 +0000 (UTC)
From: "David Valeri (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1322604133.28145.1304686923153.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1662021890.79453.1303713545673.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-3899) Add support for Camel property
 placeholders in the TLS configuration in the XML DSLs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029923#comment-13029923 ] 

David Valeri commented on CAMEL-3899:
-------------------------------------

I like this idea, but it brings us back to the situation where the hierarchy for the TLS configuration is bound to a single Camel context.  See the comment thread in the main issue (CAMEL-3750) for the full details, but Willem had suggested to leave the TLS configuration portable across multiple contexts by removing the dependency on the context after we discussed the utility, or potential lack there of, of using ClassResolver as opposed to the original resource resolving logic.

It sounds like this is a use case that could warrant reintroducing the dependency on the CamelContext.

> Add support for Camel property placeholders in the TLS configuration in the XML DSLs
> ------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3899
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3899
>             Project: Camel
>          Issue Type: Sub-task
>          Components: camel-core, camel-http, camel-jetty
>            Reporter: Claus Ibsen
>             Fix For: 2.8.0
>
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira