Return-Path: X-Original-To: apmail-cocoon-dev-archive@www.apache.org Delivered-To: apmail-cocoon-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 0F9BB75F0 for ; Thu, 14 Jul 2011 09:13:33 +0000 (UTC) Received: (qmail 67242 invoked by uid 500); 14 Jul 2011 09:13:31 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 66889 invoked by uid 500); 14 Jul 2011 09:13:14 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 66881 invoked by uid 99); 14 Jul 2011 09:13:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jul 2011 09:13:09 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of simone.tripodi@gmail.com designates 74.125.83.51 as permitted sender) Received: from [74.125.83.51] (HELO mail-gw0-f51.google.com) (74.125.83.51) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jul 2011 09:13:03 +0000 Received: by gwj17 with SMTP id 17so20275gwj.24 for ; Thu, 14 Jul 2011 02:12:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=eIUghD07qU4aAvlVUFcZXPlhaSL5PnqdBADBeYj5Eys=; b=Etu1bC6TvhIUFrh7kVl6eUjVGvsSGnU83obhIP5m5VTYDENVM7J8bTmX+QB64+7a3+ 2WApQ6WoW3WmC6YVqZdybdJs15URl+Jeti1Ygfo0lW+JPu4mAR775acPec8+tTaIlHPP b5FwzKKtGsnJVcc7Dy7YcuoIbWgrXSfiq1SY8= MIME-Version: 1.0 Received: by 10.150.184.19 with SMTP id h19mr2251397ybf.343.1310634762405; Thu, 14 Jul 2011 02:12:42 -0700 (PDT) Sender: simone.tripodi@gmail.com Received: by 10.151.48.15 with HTTP; Thu, 14 Jul 2011 02:12:42 -0700 (PDT) In-Reply-To: <4E1D498F.8050009@indoqa.com> References: <7C655C04B6F59643A1EF66056C0E095EA99D01@eusex01.sweden.ecsoft> <4E1D498F.8050009@indoqa.com> Date: Thu, 14 Jul 2011 11:12:42 +0200 X-Google-Sender-Auth: PRTnVjRV_9DXxO0b9W9cFuHM9qg Message-ID: Subject: Re: Using XQJ API with Cocoon3 From: Simone Tripodi To: dev@cocoon.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Steven!!! +1 to your suggestion. I've never been fan of 'optional' module that aggregates every 3rd parties integrations, I'd like to see it rather splitted in a multi-module structure. Please let me know if you want me to work on it, I'll fill an issue on JIRA and work. TIA, have a nice day!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Wed, Jul 13, 2011 at 9:30 AM, Steven Dolg wrote= : > Am 05.07.2011 14:49, schrieb Simone Tripodi: >> >> Hi Robby!!! >> as I wrote you on Twitter, this is something *really* interesting that >> must be included in the Cocoon distribution :) >> >> We can include that module quite easy, all you have to do is >> >> =C2=A0* checkout/update the C3 /trunk; >> =C2=A0* add needed dependencies in the =C2=A0in = the >> /parent/pom.xml >> =C2=A0* add your code in the /cocoon-optional module in a proper package= - >> see the existing codebase as samples how we already managed 3rd >> parties integrations >> =C2=A0* make a patch and submit it on JIRA > > Hey, > > a little late to the party, but I wanted to add some comments. > > We should take a look at introducing "topic" specific modules. > I fear that the optional module turns into a giant clump of all things > unrelated. > > That's pretty much the opposite of the original intention: > Have small, lightweight modules that you choose to use based on your actu= al > requirements, allowing you to tailor your application package exactly to > your needs. > If I'm forced to use the optional module that brings dozens (::hyperbole:= :) > of undesired features and dependencies just because I need one very speci= fic > feature, I'd be a little upset. > (I don't like uploading 100 MB war files :/ ) > > > But I wholeheartedly agree to the feature idea. DO WANT! :P > > Cheers, > Steven >> >> Looking forward to hear from you soon, all the best!!! >> Simo >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> >> >> On Tue, Jul 5, 2011 at 2:42 PM, Robby Pelssers >> =C2=A0wrote: >>> >>> Hi all, >>> >>> As Cocoon is an excellent framework for dealing with XML and hence in a >>> lot of cases is stored in a XML Database it makes sense to offer out-of= -the >>> box functionality to extract data from it. =C2=A0From my personal exper= ience I >>> think most XMLDB implementers have abondoned the XMLDB API initiative a= nd >>> are focusing on XQuery for Java (XQJ) instead. >>> >>> I just started playing with the API today and wrote a bit of code to ge= t >>> more acquainted. =C2=A0I would like to start a little thread to find ou= t if we >>> can add a new XQJGenerator to the optional cocoon module. >>> >>> A first little exercise is mentioned on my blog but it's far from >>> production ready. >>> >>> - TODO: allow wrapping query result in 1 root tag >>> - Problem: the XQJ interface jar is packaged along with the >>> implementations (Sedna, Exist, Marklogic). =C2=A0This means I had to ac= tually >>> declare a maven dependency on the implementation specific jar (in this = case >>> sedna-xqj-beta-5.jar). >>> >>> For the ones who think this would be a great add-on, check my first pos= t >>> at http://robbypelssers.blogspot.com/2011/07/using-xqj-api-with-cocoon3= .html >>> >>> Kind regards, >>> Robby Pelssers >>> > >