Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CF2FB200CC2 for ; Wed, 5 Jul 2017 17:37:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CD800163AA6; Wed, 5 Jul 2017 15:37:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 20558163AA4 for ; Wed, 5 Jul 2017 17:37:08 +0200 (CEST) Received: (qmail 47524 invoked by uid 500); 5 Jul 2017 15:37:08 -0000 Mailing-List: contact issues-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 issues@camel.apache.org Received: (qmail 47515 invoked by uid 99); 5 Jul 2017 15:37:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jul 2017 15:37:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id DB313C089C for ; Wed, 5 Jul 2017 15:37:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.011 X-Spam-Level: X-Spam-Status: No, score=-100.011 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id yqSRBeSBW-cs for ; Wed, 5 Jul 2017 15:37:07 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id B74725FBBB for ; Wed, 5 Jul 2017 15:37:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D269CE0D73 for ; Wed, 5 Jul 2017 15:37:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3DBAD24630 for ; Wed, 5 Jul 2017 15:37:00 +0000 (UTC) Date: Wed, 5 Jul 2017 15:37:00 +0000 (UTC) From: "John Poth (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-11513) camel-salesforce - add undertow support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 05 Jul 2017 15:37:10 -0000 John Poth created CAMEL-11513: --------------------------------- Summary: camel-salesforce - add undertow support Key: CAMEL-11513 URL: https://issues.apache.org/jira/browse/CAMEL-11513 Project: Camel Issue Type: Improvement Components: camel-salesforce Affects Versions: 2.19.1 Reporter: John Poth It would be nice to have the option to use undertow as the underlying http client for camel-salesforce. Here's a summary following a duscussion with [~zregvart]: * We could have an abstraction which would allow the option to use jetty/undertow (default being jetty) * We currently rely on CometD for streaming which only supports Jetty. We would need to rebuild that with websocket/long polling from undertow. Ideas/opinions are welcome! -- This message was sent by Atlassian JIRA (v6.4.14#64029)