Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 7 Sep 2015 09:39:45 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12862158.1441610993000.271567.1441618785817@Atlassian.JIRA>
In-Reply-To: <JIRA.12862158.1441610993000@Atlassian.JIRA>
References: <JIRA.12862158.1441610993000@Atlassian.JIRA>
 <JIRA.12862158.1441610993060@arcas>
Subject: [jira] [Resolved] (CAMEL-9116) camel-sjms - Should use same binding
 to/from JMS messages as camel-jms
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-9116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-9116.
--------------------------------
    Resolution: Fixed

> camel-sjms - Should use same binding to/from JMS messages as camel-jms
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-9116
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9116
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-sjms
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.16.0
>
>
> This allows end users to switch between camel-jms and camel-sjms easier. Also camel-jms has been proven for a longer time, and would be better if camel-sjms supports and is more similar to some of the functions it has.
> The binding between JMS and Camel should be a good start to make that the same/similar as in JMS.
> See nabble
> http://camel.465427.n5.nabble.com/Camel-SJMS-cannot-convert-Jetty-objects-to-JMS-object-tp5771193.html


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)