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 2496B11890 for ; Tue, 24 Jun 2014 15:47:28 +0000 (UTC) Received: (qmail 42525 invoked by uid 500); 24 Jun 2014 15:47:27 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 42483 invoked by uid 500); 24 Jun 2014 15:47:27 -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 42210 invoked by uid 99); 24 Jun 2014 15:47:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jun 2014 15:47:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sstults@opensourceconnections.com designates 209.85.213.54 as permitted sender) Received: from [209.85.213.54] (HELO mail-yh0-f54.google.com) (209.85.213.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jun 2014 15:47:24 +0000 Received: by mail-yh0-f54.google.com with SMTP id i57so302458yha.13 for ; Tue, 24 Jun 2014 08:46:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=C/bdy7k2lgN9yyUOc8aoGEpOSQ1D+45qJEto7/9CU/M=; b=OQKwIVOvJdbttbm4DLBE701OkY8WyPZ+tCNxoYSZHK2zVMvqdaPg8NNXCb2kA4Y1ll nsd7wAfqYq/bUAatmA6N2Q2LvPCtmIVesnQxO9350YM3ENSx499W7Rc+NT5Ir7zYOiK3 ZIn/c5GEpy4iXOvBC8J7RsYoOaq7KpzlF/nxC5OwliSO7K6i/+wNQtd2TO9901NF1nD+ GW3+sbL2WWJAl1Lc6vp/GPnqjC3I7fhepNiFLSvJq+fZqLrjPZtJoXqAntIyRkrQz44F yGuEnn5mi4RPu7CZdEzvZH6LVaZ207IdHUr/r0JvS0sghHxM0Cwhh1IH7C05eo0pOMwL +RDg== X-Gm-Message-State: ALoCoQkvvx9fcTGe5gMP5OmH7HNz0rOV+p+iP8d0Zh/GmAxBqeFb0ogNhjGDsTu/iev3M9aelSan MIME-Version: 1.0 X-Received: by 10.236.216.16 with SMTP id f16mr2651204yhp.90.1403624819344; Tue, 24 Jun 2014 08:46:59 -0700 (PDT) Received: by 10.170.190.7 with HTTP; Tue, 24 Jun 2014 08:46:59 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Jun 2014 11:46:59 -0400 Message-ID: Subject: Re: camel-solr, SSL, and SolrCloud From: Scott Stults To: users@camel.apache.org Content-Type: multipart/alternative; boundary=001a1133d776c15d8a04fc96de6a X-Virus-Checked: Checked by ClamAV on apache.org --001a1133d776c15d8a04fc96de6a Content-Type: text/plain; charset=ISO-8859-1 Sure can! In fact that'd be the easiest. I'll make sure it's go and send a pull request. Is there something I should do with Jira as well? -Scott On Tue, Jun 24, 2014 at 11:09 AM, Claus Ibsen wrote: > Hi > > Can it be in the existing camel-solr component? > > On Tue, Jun 24, 2014 at 4:55 PM, Scott Stults > wrote: > > Hello Camel Users! > > > > My company has been doing a lot with the camel-solr component and we > > recently added SSL and SolrCloud support. We'd like to submit this back > to > > Camel, so my question is whether we should make this a patch of > camel-solr > > or create a completely separate component (maybe camel-solrs or > > camel-solrcloud). > > > > Do you have a preference? > > > > > > Thank you, > > Scott > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cibsen@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > hawtio: http://hawt.io/ > fabric8: http://fabric8.io/ > -- Scott Stults | Founder & Solutions Architect | OpenSource Connections, LLC | 434.409.2780 http://www.opensourceconnections.com --001a1133d776c15d8a04fc96de6a--