Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6C35611278 for ; Tue, 16 Sep 2014 21:19:34 +0000 (UTC) Received: (qmail 7784 invoked by uid 500); 16 Sep 2014 21:19:34 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 7743 invoked by uid 500); 16 Sep 2014 21:19:34 -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 7733 invoked by uid 99); 16 Sep 2014 21:19:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 21:19:34 +0000 Date: Tue, 16 Sep 2014 21:19:34 +0000 (UTC) From: "Scott England-Sullivan (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CAMEL-6180) SJMS Component behavior suggestions to improve upon the standard JMS component MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-6180?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1413= 6247#comment-14136247 ]=20 Scott England-Sullivan commented on CAMEL-6180: ----------------------------------------------- Hi Randy, Regarding number #5, see CAMEL-7825. Work is now in progress via contribut= ion by Andrew Block. Thanks, Scott ES > SJMS Component behavior suggestions to improve upon the standard JMS comp= onent > -------------------------------------------------------------------------= ----- > > Key: CAMEL-6180 > URL: https://issues.apache.org/jira/browse/CAMEL-6180 > Project: Camel > Issue Type: Improvement > Components: camel-sjms > Reporter: Matt Pavlovich > Assignee: Scott England-Sullivan > > The SJMS component should not suffer any feature loss from the standard J= MS component, for best user experience in 3.0.=20 > A random mix of suggested behavior changes/enhancements: > 1. Supporting things like consume from multiple destinations using wildc= ards... from jms:queue:US_TICKETS_* =C2=A0 > 2. Support dynamic destination on a CamelJmsDestination=09javax.jms.Destination=09 A destination object= . > CamelJmsDestinationName=09String=09 The destination name. > 3. I suggest making 'request-reply' be explicit, since implicit is reall= y painful for new users. The "magic" temp destination listener is not confu= sing and the user has nothing in the route to go on as to why that is happe= ning. > 4. Along w/ #3, don't kill the QoS headers by default. It makes setting = up proxies really complicated.=20 > 5. Support MQ Series 'weirdness' that current component handles.. see 'S= etting JMS provider options on the destination' here: http://camel.apache.o= rg/jms.html > Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)