Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 33103 invoked from network); 17 Feb 2011 22:16:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2011 22:16:10 -0000 Received: (qmail 75855 invoked by uid 500); 17 Feb 2011 22:16:10 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 75811 invoked by uid 500); 17 Feb 2011 22:16:10 -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 75801 invoked by uid 99); 17 Feb 2011 22:16:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 22:16:10 +0000 X-ASF-Spam-Status: No, hits=0.3 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of cschneider@talend.com does not designate 83.246.65.53 as permitted sender) Received: from [83.246.65.53] (HELO relay03-haj2.antispameurope.com) (83.246.65.53) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 22:16:04 +0000 Received: from mail.sfp-net.com (smtp.sfp-net.com [83.220.139.247]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by relay03-haj2.antispameurope.com (ASE-Secure-MTA) with ESMTP id 5D79C63C09B for ; Thu, 17 Feb 2011 23:15:42 +0100 (CET) Received: from EXMBX01.SFP-Net.skyfillers.local ([172.16.12.11]) by EXHUB02.SFP-Net.skyfillers.local ([172.16.12.23]) with mapi; Thu, 17 Feb 2011 23:15:42 +0100 From: Christian Schneider To: "users@camel.apache.org" Date: Thu, 17 Feb 2011 23:15:37 +0100 Subject: AW: Camel Osgi JMS Thread-Topic: Camel Osgi JMS Thread-Index: AQHLzuLdUlBpx3+dBkSgEGFyt8rNdJQGPROAgAADkU6AAAGCcA== Message-ID: References: , In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE, en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Roshan, may I ask what you want to achieve by setting the connection factory from t= he url? If you only want to use several connection factories at the same time you c= an simply create several jms components with different names. Christian -----Urspr=FCngliche Nachricht----- Von: Roshan A. Punnoose [mailto:rpunnoose@proteuseng.com]=20 Gesendet: Donnerstag, 17. Februar 2011 23:08 An: users@camel.apache.org Betreff: RE: Camel Osgi JMS Yeah, that's what I expected. Thanks! I think that last solution would work= in the short term, but I also created a component that added a "connection= FactoryName" parameter, so now my string looks like: "myjms:topic:heartBeatWithCounts?connectionFactoryName=3Djavax.jms.Connecti= onFactory" Where it looks up the ConnectionFactory in the camel registry (aka the osgi= service registry) Works for now, but we'll see.=20 Thanks for all your help guys. Roshan ________________________________________ From: Christian Schneider [cschneider@talend.com] Sent: Thursday, February 17, 2011 5:06 PM To: users@camel.apache.org Subject: AW: Camel Osgi JMS Hi Roshan, I don=B4t think you can reference the connectionfactory from the endpoint u= rl. I may be wrong though. What you can easily do is set up a jms component in spring and reference th= e connectionfactory through a service reference. Perhaps this is already what you need: If you don=B4t want to use spring for it you can do the same in java: JmsComponent jmsComponent =3D new JmsComponent(); jmsComponent.setConnectio= nFactory(cf); camelContext.addComponent("jms", jmsComponent); You will only have to retrieve the connection factory from a service tracke= r or the camel registry. Christian -----Urspr=FCngliche Nachricht----- Von: Roshan A. Punnoose [mailto:rpunnoose@proteuseng.com] Gesendet: Donnerstag, 17. Februar 2011 21:40 An: users@camel.apache.org Betreff: Camel Osgi JMS Usually we use spring to set up the camel jms component before using, but I= wanted to know if it is possible to reference any bean in the camel regist= ry by name for the connectionFactory. For example, let's say that I have the jms connection factory exposed as an= osgi service in my container. Thanks to camel, I can actually search the o= sgi service registry with my camel registry by just asking for any bean wit= h name "javax.jms.ConnectionFactory". That will return the first JMS Connec= tion Factory as a bean from teh camel/osgi registry. Is there anyway in the= camel-jms component to do something where I can refer to that connection f= actory instead of writing up a spring configuration to do the same? Something like: from("jms:topic:heartBeatWithCounts?connectionFactory=3Djavax.jms.Connectio= nFactory") Roshan -- Follow this link to mark it as spam: http://mailfilter.proteus-technologies.com/cgi-bin/learn-msg.cgi?id=3DECEF0= 27DF1.A1454