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 57261C10C for ; Fri, 20 Apr 2012 00:40:27 +0000 (UTC) Received: (qmail 3003 invoked by uid 500); 20 Apr 2012 00:40:26 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 2927 invoked by uid 500); 20 Apr 2012 00:40:26 -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 2919 invoked by uid 99); 20 Apr 2012 00:40:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2012 00:40:26 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com designates 209.85.160.45 as permitted sender) Received: from [209.85.160.45] (HELO mail-pb0-f45.google.com) (209.85.160.45) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2012 00:40:20 +0000 Received: by pbcuo5 with SMTP id uo5so419807pbc.32 for ; Thu, 19 Apr 2012 17:39:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=hV1BaQyaMiAOmZlOAWekw9lP3nfthyUN+vu2To0+Ca4=; b=HVBwnzOAuJR8VhAl8OdvUArr4KgLf0hgssL+/SZTGHOjd4OHsCwvZuG23mweJ/Qa2J SBKGTtpSSTB35AH4stQRvYLTl3SbR8qnBv5SL+pvcBrUTzYnhprmkjGLTthi/6NmZ1ac hGOrshRKZBUpxXpEiUxGzFouP661viR/lrGQYSQQf3xOvG8ID1ryzBMXgNTedIZ39aKe Ue/Sd7yGj42KBkZ2ldAd6KChA6hsQuqQ+BzqrDeomAPwmaqlifN6Acg4pUhDWptaHK5m eqUXqyW0CpFse/4qt1yqeb+tLakVeEf5PxpW88vTqR+2c1zNfRhnHhBpuSf6NcpQKUQs wq+Q== Received: by 10.68.227.134 with SMTP id sa6mr8431390pbc.101.1334882399099; Thu, 19 Apr 2012 17:39:59 -0700 (PDT) Received: from [192.168.0.158] ([125.33.124.223]) by mx.google.com with ESMTPS id pg6sm3670107pbb.41.2012.04.19.17.39.55 (version=SSLv3 cipher=OTHER); Thu, 19 Apr 2012 17:39:57 -0700 (PDT) Message-ID: <4F90B059.3080709@gmail.com> Date: Fri, 20 Apr 2012 08:39:53 +0800 From: Willem Jiang User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: users@camel.apache.org Subject: Re: SSL and CXF Consumers References: <1334327877568-5638480.post@n5.nabble.com> <1334676965139-5646855.post@n5.nabble.com> <4F8FC9B4.8020602@gmail.com> <1334850172682-5652117.post@n5.nabble.com> <1334875220841-5652965.post@n5.nabble.com> In-Reply-To: <1334875220841-5652965.post@n5.nabble.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On Fri Apr 20 06:40:20 2012, Castyn wrote: > Thanks for the reply, I will work through some of the configuration shortly. > I did however notice that when I changed my cxf consumer to use an address > of https, that my route would no longer deploy saying that SSL protocol > could not be used on an http configured endpoint. > > Looking deeper it looks like I might need to actually use the jetty engine > to setup the SSL port for that CXF consumer? If you are using the CXF Servlet transport, you don't need to setup the jetty engine. If not, you should setup the jetty engine as the example does. > > -- > View this message in context: http://camel.465427.n5.nabble.com/SSL-and-CXF-Consumers-tp5638480p5652965.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Willem ---------------------------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Web: http://www.fusesource.com Blog: http://willemjiang.blogspot.com (English) http://jnn.javaeye.com (Chinese) Twitter: willemjiang Weibo: willemjiang