Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4271299F3 for ; Wed, 22 Feb 2012 15:52:41 +0000 (UTC) Received: (qmail 97144 invoked by uid 500); 22 Feb 2012 15:52:41 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 97042 invoked by uid 500); 22 Feb 2012 15:52:40 -0000 Mailing-List: contact dev-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 dev@camel.apache.org Received: (qmail 97034 invoked by uid 99); 22 Feb 2012 15:52:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Feb 2012 15:52:40 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of chsnow123@gmail.com designates 209.85.213.45 as permitted sender) Received: from [209.85.213.45] (HELO mail-yw0-f45.google.com) (209.85.213.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Feb 2012 15:52:33 +0000 Received: by yhjj63 with SMTP id j63so120480yhj.32 for ; Wed, 22 Feb 2012 07:52:12 -0800 (PST) Received-SPF: pass (google.com: domain of chsnow123@gmail.com designates 10.236.157.9 as permitted sender) client-ip=10.236.157.9; Authentication-Results: mr.google.com; spf=pass (google.com: domain of chsnow123@gmail.com designates 10.236.157.9 as permitted sender) smtp.mail=chsnow123@gmail.com; dkim=pass header.i=chsnow123@gmail.com Received: from mr.google.com ([10.236.157.9]) by 10.236.157.9 with SMTP id n9mr43197107yhk.96.1329925932391 (num_hops = 1); Wed, 22 Feb 2012 07:52:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=+DG1hQBO622QC0OXF5qYubQFJVbAS6o6b/dZZeo5Lm4=; b=QvpdX/FqlzGES8yzyrjI2SmHt7paxv01EYNM78iXNjKLsu8G1GywadPnWu+ULGK5YZ zwLKWM16fc5qgUF1D6izUBP5I/FTzP+UVFZ//BaGEGE3HJe7VEnUyh81DddTWdw2gIoY e/Opf7IX0s2yuTSCp01QsFWPqA0k2i8oTt35g= MIME-Version: 1.0 Received: by 10.236.157.9 with SMTP id n9mr33722507yhk.96.1329925932343; Wed, 22 Feb 2012 07:52:12 -0800 (PST) Received: by 10.236.66.100 with HTTP; Wed, 22 Feb 2012 07:52:12 -0800 (PST) Date: Wed, 22 Feb 2012 15:52:12 +0000 Message-ID: Subject: adding camel-smpp URI options From: chris snow To: dev@camel.apache.org Content-Type: multipart/alternative; boundary=20cf303f6794c661cb04b98f8230 X-Virus-Checked: Checked by ClamAV on apache.org --20cf303f6794c661cb04b98f8230 Content-Type: text/plain; charset=ISO-8859-1 I have a requirement to be able to configure the camel-smpp component by providing it with a custom smpp and smpps socketfactory. The custom socketfactory is needed in my environment to provide HTTP CONNECT proxy support. Does it make sense to add the following two URI options? smppSocketFactoryClass smppsSocketFactoryClass If these options aren't set, the smpp component will use the default socket factories. If this is ok, I'll submit a patch. Many thanks, Chris --20cf303f6794c661cb04b98f8230--