Return-Path: X-Original-To: apmail-river-dev-archive@www.apache.org Delivered-To: apmail-river-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7847110DBD for ; Sun, 9 Mar 2014 21:55:53 +0000 (UTC) Received: (qmail 9579 invoked by uid 500); 9 Mar 2014 21:55:52 -0000 Delivered-To: apmail-river-dev-archive@river.apache.org Received: (qmail 9557 invoked by uid 500); 9 Mar 2014 21:55:52 -0000 Mailing-List: contact dev-help@river.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@river.apache.org Delivered-To: mailing list dev@river.apache.org Received: (qmail 9547 invoked by uid 99); 9 Mar 2014 21:55:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Mar 2014 21:55:51 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.215.176] (HELO mail-ea0-f176.google.com) (209.85.215.176) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Mar 2014 21:55:45 +0000 Received: by mail-ea0-f176.google.com with SMTP id o10so3303668eaj.21 for ; Sun, 09 Mar 2014 14:55:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xpro.biz; s=google; h=from:to:subject:date:message-id:organization:user-agent:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=b8JymQnOAU+xsffdj/tcwHzCJO59IvmYeUxFGTxKcqs=; b=L1ESEutyzMS5JBBJO/C9m/k1kiBvgyfVaiwNKIlrFclJzfzjE6A/tyJS5AskAtCfAS XoiiGW2IsiYmv1w+u/5K4GREIlBMT8SXJNN1Y/PqZ2iuVh6p6zjpRpHEMxZsgMChGjL+ 7DSSycEZNQDMHS+zb48+Pie8svneav5vMuwFM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version:content-type :content-transfer-encoding; bh=b8JymQnOAU+xsffdj/tcwHzCJO59IvmYeUxFGTxKcqs=; b=UnSEZQFitqx3LBG2tPCBrA4gZBKhcNnwT4QHyUaSFRp67EcI7PwbzykvCAjsdCZY4w ddq9HzWM+idMRodAh6njcmiTkb0XITTNw1svf755HaTPm2OufvSC6f260ePFN8WrZ581 cEeliV1uYioZYiTD/KsOd+f5vWs7/1yFUVTAtGXdRvxe2WVC41WJABMrWmO6GCdxcUp3 3qo2uKDyaEU1eEE6o2KrBfHRojUw1TPXDf3sZRnVJWAH0dkn98E3OVOSGq0hDPe/7N0I fWw6B7U9pQDJoQ69BYLpGTHeppyqiQNS8DoXaI1UKkyBbS8ZJqI+E4NfCRIRWZAjhqa1 E0TA== X-Gm-Message-State: ALoCoQmNF+fxLIVd2c04Eo/AcZnrEQNGrnShjwpe1hxT1+Gg65zYLo3KLKNcc+zJauXuP7XpyA1i X-Received: by 10.14.107.129 with SMTP id o1mr30929eeg.99.1394402124541; Sun, 09 Mar 2014 14:55:24 -0700 (PDT) Received: from mkleczek-laptop.localnet (ope185.internetdsl.tpnet.pl. [83.0.28.185]) by mx.google.com with ESMTPSA id m1sm37178779een.7.2014.03.09.14.55.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 09 Mar 2014 14:55:23 -0700 (PDT) From: =?utf-8?B?TWljaGHFgiBLxYJlY3plaw==?= To: dev@river.apache.org Subject: Re: River-436 - need some explanation of preferred class provider Date: Sun, 09 Mar 2014 22:54:57 +0100 Message-ID: <3385989.DM6O1PcaKA@mkleczek-laptop> Organization: XPro Sp. z o. o. User-Agent: KMail/4.11.5 (Linux/3.11.10-7-desktop; KDE/4.11.5; x86_64; ; ) In-Reply-To: <1715328B-8FCA-40E5-8C25-8EB69F0F477B@cox.net> References: <5313816B.9030703@xpro.biz> <1715328B-8FCA-40E5-8C25-8EB69F0F477B@cox.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="nextPart1716649.e274GEmRRP" Content-Transfer-Encoding: 7Bit X-Virus-Checked: Checked by ClamAV on apache.org --nextPart1716649.e274GEmRRP Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" The whole point of my example is that the client has no knowledge of Ut= il=20 interface - it is simply not interested in it. The problem is not that the client cannot plug-in RMIClassProvider=20 dynamically. It is just that with current format of codebase annotation= the=20 client cannot do anything. It simply does not have enough data to decid= e what=20 to do - just two lists of URLs without any dependency information encod= ed. Regards, On Sunday, March 09, 2014 02:33:03 PM Gregg Wonderly wrote: > All you have to provide in the client is a class loading implementati= on that > knows about Util and pins it into a parent class loader from the clas= s > loaders that proxies load. I netbeans, this happens because meta dat= a > declares that such a relationship exists. In OSGi, this happens beca= use > meta data declares that such a relationship exists. All you have to = do, is > create meta data that specifies that such a relationship exists, and = then > plug in a River-336 compatible class loading implementation in your c= lient. >=20 > My point is no that River-336 provides the answer, but rather it prov= ides a > mechanism that an application can use. Not every application has suc= h a > need, and not every known implementation uses the same model. Thus, = there > isn=E2=80=99t a single answer that can exist ahead of time. >=20 > If you want to use OSGi, plug it in. If you want to use Netbeans, pl= ug it > in. If you want to use both at the same time, work it out and plug = it in. > There is room for a single standard to eventually win. But, there i= sn=E2=80=99t a > single standard that is standing alone right now that I see. >=20 > Gregg Wonderly --=20 Micha=C5=82 K=C5=82eczek XPro Sp. z o. o. ul. Borowskiego 2 03-475 Warszawa Polska --nextPart1716649.e274GEmRRP Content-Disposition: attachment; filename*=UTF-8''Micha%C5%82%20K%C5%82eczek%20%28XPro%29%2Evcf Content-Transfer-Encoding: quoted-printable Content-Type: text/vcard; charset="utf-8"; name*=utf-8''Micha%C5%82%20K%C5%82eczek%20%28XPro%29%2Evcf BEGIN:VCARD=0D ADR;TYPE=3Dpref;TYPE=3Dwork:;;ul. Borowskiego 2;Warszawa;;03-475;Poland= =0D EMAIL:michal.kleczek@xpro.biz=0D FN:Micha=C5=82 K=C5=82eczek=0D N:K=C5=82eczek;Micha=C5=82;;;=0D ORG:XPro Sp. z o. o.=0D UID:Zp8UeLZmq5=0D VERSION:3.0=0D END:VCARD=0D =0D --nextPart1716649.e274GEmRRP--