Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 51828 invoked from network); 3 Mar 2009 07:03:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2009 07:03:51 -0000 Received: (qmail 43318 invoked by uid 500); 3 Mar 2009 07:03:51 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 43301 invoked by uid 500); 3 Mar 2009 07:03:50 -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 43290 invoked by uid 500); 3 Mar 2009 07:03:50 -0000 Delivered-To: apmail-activemq-camel-user@activemq.apache.org Received: (qmail 43287 invoked by uid 99); 3 Mar 2009 07:03:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2009 23:03:50 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 07:03:43 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LeOew-0003ag-HF for camel-user@activemq.apache.org; Mon, 02 Mar 2009 23:03:22 -0800 Message-ID: <22303475.post@talk.nabble.com> Date: Mon, 2 Mar 2009 23:03:22 -0800 (PST) From: atlep To: camel-user@activemq.apache.org Subject: Classloading and OSGI MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: atle.prange@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org I am using camel in a OSGI (Felix) environment, and I regularly bump into classloading issues: THe most recentones are The JSM Component cant find the QueueBrowserStrategy because it cannot see the spring bundle that exports it, because it is using a "wrong " classloader to try to load it (it uses o.a.c.util.ObjectHelper's classloader). The activemq component cannot load object messages because it cannot deserialize the body. I have tried setting the thread contextclassloader to my bundles classloader, but it seems it does not use the context classloader. Are there any good practices or patterns regarding using camel + activemq in a OSGi environment, without resorting to servicemix? Maybe these wrinkles are ironed out in camel 2.0? -- View this message in context: http://www.nabble.com/Classloading-and-OSGI-tp22303475p22303475.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.