Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 2274 invoked from network); 15 Apr 2010 17:47:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Apr 2010 17:47:46 -0000 Received: (qmail 26616 invoked by uid 500); 15 Apr 2010 17:47:45 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 26574 invoked by uid 500); 15 Apr 2010 17:47:45 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 26566 invoked by uid 99); 15 Apr 2010 17:47:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Apr 2010 17:47:45 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of earcam@gmail.com designates 74.125.82.48 as permitted sender) Received: from [74.125.82.48] (HELO mail-ww0-f48.google.com) (74.125.82.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Apr 2010 17:47:40 +0000 Received: by wwb29 with SMTP id 29so1008494wwb.35 for ; Thu, 15 Apr 2010 10:47:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type; bh=d+nrQmyPICQFMJHG2LseNIVqWtU8VcTjq4PfSY9W4Cg=; b=okL6J9F6P1D4eKRnXBhiTdnymutg2iMk/af3OFNAB+UEbPrVxFoS0TqWGXY8uYr2lZ On7FeH2L/DvT/EWQOL0nrrpSNjI388EB3SMKYl3ZdQypssYI1Z1knNnVO2dQ6hfOyaGo +gHa5oycwmtnSrAwjS+AELmxXrzbk5CsRdKxo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=Js68JjYC32wlr+2QTxJW6NDj6+mPZLynf8CgNnjkcwXcqwJpg6AEfTwUx9vTNMNdPy iySHsGuA8BUGpmTIIFz2O6PF9DE9bU0l9yvnj7D4j1PDHvb46Ly5d3z9MuMovIzd4h72 zpKl9rr/Me7ySDPjT8+daElQDsmlSxBJ5YrRo= MIME-Version: 1.0 Received: by 10.216.49.84 with HTTP; Thu, 15 Apr 2010 10:40:13 -0700 (PDT) In-Reply-To: References: <42721ED4-DC28-47AF-A456-D3FF321013EF@richrelevance.com> <76A09B97FD0B434ABCD9A75F688CF7E50373D81E@hq-ex-mb01.ad.navteq.com> <9825E237-841F-4B16-A8A8-13B30C2E4051@consol.de> From: Caspar MacRae Date: Thu, 15 Apr 2010 18:40:13 +0100 Received: by 10.216.178.85 with SMTP id e63mr395702wem.156.1271353638519; Thu, 15 Apr 2010 10:47:18 -0700 (PDT) Message-ID: Subject: Re: Custom Class Loader for Hadoop M/R jobs? To: general@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e65b61d00202f404844a1659 --0016e65b61d00202f404844a1659 Content-Type: text/plain; charset=UTF-8 ServiceMix and ActiveMQ are also using OSGi in their core AFAIK. The way this (these) problems have been solved is more of an afterthought, and regardless is quite simplistic (thinking of classloader isolation in web containers, app servers, and the monolithic WARs produced as a result), however OSGi's approach to modularity provides a truly elegant solution. wrt to the ticket https://issues.apache.org/jira/browse/MAPREDUCE-243, Dave Savage is a nice chap who works for Paremus (an enterprise OSGi provider) I spoke with him at the recent OSGi devcon in London and he did quite a bit of work to get this working for private clients - I'm sure with his expertise it would not be a huge effort to get this rolling again. On 15 April 2010 18:23, Segel, Mike wrote: > Ok, so are you using OSGi's code, or just writing your own code to > implement a published API/specification? > > I realize this is getting off topic, so you may just want to e-mail me > directly. > > Thx > > -Mike > > -----Original Message----- > From: Marcel May [mailto:marcel.may@consol.de] > Sent: Thursday, April 15, 2010 11:35 AM > To: general@hadoop.apache.org > Subject: Re: Custom Class Loader for Hadoop M/R jobs? > > > On Apr 15, 2010, at 6:27 PM, Segel, Mike wrote: > > > Caspar, > > > > While IANAL, I did a first blush read of OSGi's Specification License, > Version 1.0. on the website link: > http://www.osgi.org/Specifications/Licensing as well as the license on the > download page: http://www.osgi.org/Download/Release4V42?info=nothanks. > > > > In a nutshell, OSGi's Specification License, Version 1.0. is incompatible > with Apache's. > > > > That alone can explain why Apache projects won't touch OSGi. > > > > http://felix.apache.org/ > > > From a more practical issue, this problem is solved in other Apache > projects, so why not borrow from another Apache project like Tomcat? > > > > Does that make sense? It appears OSGi is a non-starter. > > > > HTH > > > > -Mike > ... > > Cheers, > Marcel > > > The information contained in this communication may be CONFIDENTIAL and is > intended only for the use of the recipient(s) named above. If you are not > the intended recipient, you are hereby notified that any dissemination, > distribution, or copying of this communication, or any of its contents, is > strictly prohibited. If you have received this communication in error, > please notify the sender and delete/destroy the original message and any > copy of it from your computer or paper files. > --0016e65b61d00202f404844a1659--