From dev-return-73053-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Fri Apr 10 13:53:09 2009 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 45837 invoked from network); 10 Apr 2009 13:53:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Apr 2009 13:53:09 -0000 Received: (qmail 48570 invoked by uid 500); 10 Apr 2009 13:53:08 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 48464 invoked by uid 500); 10 Apr 2009 13:53:08 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 48456 invoked by uid 99); 10 Apr 2009 13:53:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Apr 2009 13:53:08 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gnodet@gmail.com designates 209.85.220.174 as permitted sender) Received: from [209.85.220.174] (HELO mail-fx0-f174.google.com) (209.85.220.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Apr 2009 13:52:59 +0000 Received: by fxm22 with SMTP id 22so2010006fxm.19 for ; Fri, 10 Apr 2009 06:52:35 -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 :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=pOMaIWwoGJkztLszDGTyug6w4boBRdE21/MKs9GIuOQ=; b=D1nTKKdFE2kZ3Vf5As1RF+Te+OR27jqCmxGTjppNZ14vtFPOqLSBfAzFSVpgcdp8Hv tNvjj7daIRz/2KnxyeOu7xyKruD0OTnZtb8tXJsT8MvAZHeaPWENtkAYR53jWFNk20SC gqnRPPV03QukIuG8Jpr/hs5iF157BkfRmHe1Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=apTjnkPYzOT57VqPbORQLlwJqd45z2XbFByvHUZO6rLb/cqEYP1lRUL1m3lXXz/M0N IWSy2C2zMzHiexasgQwWTRVsZ8Vg7+sN/04XCVNppXhCgrXckA++MHzGG8NlGjX9r8/2 6B68NeJD7ou7/cRAQspDvLDJyD9UGiZ817P70= MIME-Version: 1.0 Received: by 10.223.113.3 with SMTP id y3mr161364fap.71.1239371555368; Fri, 10 Apr 2009 06:52:35 -0700 (PDT) In-Reply-To: References: <19e0530f0903170558s2048dd2cy1ca802639fb7c9b5@mail.gmail.com> <49D3462E.70401@gmail.com> <5eb405c70904081023p5b0c82cfoe14c3b11245e0c74@mail.gmail.com> <49DF3099.6090102@gmail.com> Date: Fri, 10 Apr 2009 15:52:35 +0200 Message-ID: Subject: Re: [OSGi] Support for RFC 124? From: Guillaume Nodet To: dev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org I forgot one thing about JAXB which is the fact that after parsing the XML into jaxb pojos, we still need to transform those into the Blueprint metadata pojos ... On Friday, April 10, 2009, Guillaume Nodet wrote: > I've added my own work in progress at the following location: > =A0 https://svn.apache.org/repos/asf/geronimo/sandbox/gnodet/blueprint > > I'm not sure about the use of JAXB: > =A0* first, it brings an unnecessary dependency on JDK 1.6 or jaxb impl = + JDK 5. > =A0* second, I'm not sure if we would be able to handle custom > namespaces because they require passing the current element as a DOM > node, which means serializing the element back from pojos to a dom > node ... it does not sound really efficient > > Another thing is that I was thinking it might be possible at some > point to build an intermediary serialized format of the parsed > metadata at build time to avoid the cost of jaxb marshalling / xml > parsing when possible. =A0I don't recall if there is a way to customize > the jaxb generated pojos, but having them being serializable might be > a good idea... > > On Fri, Apr 10, 2009 at 13:42, Rick McGuire wrote: >> Jarek Gawor wrote: >>> >>> Btw, I checked in under >>> https://svn.apache.org/repos/asf/geronimo/sandbox/gawor/rfc124 a tiny >>> bit of code that I was playing around with to better understand RFC >>> 124. I'll keep on working and experimenting with it but anyone is >>> welcome to join. I'm planning to add some of the RFC 124 API >>> definitions next in order see what it would take to implement these >>> API. >>> >> >> I just added some concrete implementations of the reflect APIs to the tr= ee. >> >>> Jarek >>> >>> >> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > --=20 Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com