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 B76A1EE2F for ; Wed, 13 Feb 2013 15:32:48 +0000 (UTC) Received: (qmail 95316 invoked by uid 500); 13 Feb 2013 15:32:48 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 95247 invoked by uid 500); 13 Feb 2013 15:32:48 -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 95223 invoked by uid 99); 13 Feb 2013 15:32:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Feb 2013 15:32:47 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sully6768@gmail.com designates 209.85.210.43 as permitted sender) Received: from [209.85.210.43] (HELO mail-da0-f43.google.com) (209.85.210.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Feb 2013 15:32:39 +0000 Received: by mail-da0-f43.google.com with SMTP id u36so612265dak.30 for ; Wed, 13 Feb 2013 07:32:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=fTZl3hUKc71MkeEVSLdkO6GFazg0DOG0dkITypLrBzc=; b=0loLiHijmDS8K6RmBu8I6/PTJQHv3hMXyVqFx31DaEZAMp6mgfV1SSf0oh0e/NBmeU ZpkZ2+Pery9nYYeaokrVv/b3OjmjR1DN2dLpWXPH5vSqgU+GWgCFC3laW5zBeQfskOQE i3aT47CWPs2UFn7Sasc40MME6e5pPQPSX2sYh3pUMS1gKOxYh895cGg8JW8JJkBcpYfO dami/LkN8pRTY4N+avmGrVqPG5+Sz58ujCyzTwmmH1V/4DKq43w9qyQZC8Jpj7reuIoM jGRvOr6jS2zp23XsHcgubFZ99sB5nZIX5x1e096/Al/Dx7q+EISqq6zhG5c3AmmBTL9p NFmA== X-Received: by 10.66.251.129 with SMTP id zk1mr27294724pac.9.1360769538955; Wed, 13 Feb 2013 07:32:18 -0800 (PST) Received: from [198.18.66.109] ([206.15.84.247]) by mx.google.com with ESMTPS id w2sm78980544pax.22.2013.02.13.07.32.17 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Feb 2013 07:32:18 -0800 (PST) References: <511665CD.1050500@googlemail.com> <833F2274-B46E-49FF-94FF-55BCC43420F2@gmail.com> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Cc: "users@camel.apache.org" X-Mailer: iPhone Mail (10B143) From: Scott England-Sullivan Subject: Re: SJMS and InOut Date: Wed, 13 Feb 2013 07:32:16 -0800 To: "users@camel.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org Thanks for the clarification Claus. I will update the documentation and plan= for an update in a later release.=20 Best Regards, Scott ES On Feb 13, 2013, at 12:59 AM, Harald Wellmann wrote= : > Well, it should be clearly documented that inOut() does not have the > desired effect and that camel-sjms behaves differently than camel-jms > in this respect. >=20 > I can live with the current approach, and I'm eager to see a release > of camel-sjms in 2.11 to get rid of the transitive Spring dependency > in my Java EE app which is not required except by camel-jms. >=20 > But it would be useful to remove that restriction in the next release. >=20 > We use bean invocations tunnelled through JMS a lot, and it should be > possible to have InOut methods and InOnly methods in the same service > interface, tunneled through the same queue. >=20 > Best regards, > Harald