Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 773AB11F05 for ; Thu, 11 Sep 2014 21:45:52 +0000 (UTC) Received: (qmail 4082 invoked by uid 500); 11 Sep 2014 21:45:52 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 4036 invoked by uid 500); 11 Sep 2014 21:45:52 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 4025 invoked by uid 99); 11 Sep 2014 21:45:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Sep 2014 21:45:51 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of jjathman@gmail.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Sep 2014 21:45:47 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1XSCBC-0005Ip-J5 for users@camel.apache.org; Thu, 11 Sep 2014 14:45:26 -0700 Date: Thu, 11 Sep 2014 14:45:26 -0700 (PDT) From: jjathman To: users@camel.apache.org Message-ID: <1410471926578-5756368.post@n5.nabble.com> Subject: Programmatic CXF Endpoint MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org We are trying to use the CXF component to send web services requests were the endpoint we will send to is not known ahead of time. Since we are not able to configure these endpoints we are trying to create these endpoints dynamically. I suppose my first question is whether or not this is the correct way to solve this problem. Should we create a new CXFEndpoint object each time we are sending to a new remote server? For example, when we receive an incoming message, we will then need to create 1 to many outgoing messages that we will not know the endpoint of until runtime. Second question is how to enable SSL support on these programmatically created endpoints. I've tried the normal HTTP Conduit configuration but that doesn't seem to be used when the endpoint is created programmatically. Is that true or do I have something configured incorrectly? I realize this is pretty complicated, if there's anything I can do to help clarify this, please let me know. Thank you so much! -- View this message in context: http://camel.465427.n5.nabble.com/Programmatic-CXF-Endpoint-tp5756368.html Sent from the Camel - Users mailing list archive at Nabble.com.