From user-return-6380-apmail-geronimo-user-archive=geronimo.apache.org@geronimo.apache.org Wed Apr 04 22:33:56 2007 Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 20210 invoked from network); 4 Apr 2007 22:33:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Apr 2007 22:33:55 -0000 Received: (qmail 46130 invoked by uid 500); 4 Apr 2007 22:33:56 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 46102 invoked by uid 500); 4 Apr 2007 22:33:56 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 46086 invoked by uid 99); 4 Apr 2007 22:33:56 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Apr 2007 15:33:56 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of paulmcmahan@gmail.com designates 66.249.82.235 as permitted sender) Received: from [66.249.82.235] (HELO wx-out-0506.google.com) (66.249.82.235) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Apr 2007 15:33:47 -0700 Received: by wx-out-0506.google.com with SMTP id s18so332801wxc for ; Wed, 04 Apr 2007 15:33:27 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:mime-version:in-reply-to:references:content-type:message-id:from:subject:date:to:x-mailer; b=CrLvqUSmBvYljbBGvfLDXhv/MViSvHCzCKv12f0IHbXYn6FXuYDI5mGmkkMCzLxwU5WIFxN2n+y7TH3yCcbMFGc00hRgBfexttD/+F0BT8C5b2/OqlqOph9f5IBX/2+LyIj96Y82wu7Mw8BDLNJ+OwScPabY8ke07fftWFFyhCE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:mime-version:in-reply-to:references:content-type:message-id:from:subject:date:to:x-mailer; b=oSsE3eFY11AANIelBon1QsOYhDV7Fi8IkN6nNTXiitMsYOj4zKv6pMVvBwUvONtjGqeFAFJ3EuzU/snPXkKL8IJj/MZwQ03F51EEhE+CExetkanv16Xy2uwzEx30YtZl0glfUfnu8ANZMFho4pVTRE0iSGQeoufL7HFmLP/jC+Q= Received: by 10.70.125.11 with SMTP id x11mr1541427wxc.1175726007059; Wed, 04 Apr 2007 15:33:27 -0700 (PDT) Received: from ?192.168.1.100? ( [65.5.198.110]) by mx.google.com with ESMTP id 26sm1174463wra.2007.04.04.15.33.26; Wed, 04 Apr 2007 15:33:26 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <03B36D73-1CCF-4FE3-9992-1F1AE9C32F99@yahoo.com> References: <461401AB.8020505@gmail.com> <46141214.7070003@gmail.com> <758EA8BD-17F0-4C02-9AA1-9A81EF989CCB@gmail.com> <03B36D73-1CCF-4FE3-9992-1F1AE9C32F99@yahoo.com> Content-Type: multipart/alternative; boundary=Apple-Mail-5--149689887 Message-Id: <69CA3F32-663A-4AAB-A847-A6055E66EFDB@gmail.com> From: Paul McMahan Subject: Re: Running portlets in Geronimo - Documentation Date: Wed, 4 Apr 2007 18:33:25 -0400 To: user@geronimo.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-5--149689887 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Apr 4, 2007, at 6:10 PM, David Jencks wrote: > What I'm hoping for in the future for these kinds of situations is > that there can be plugins configured for each of several databases, > e.g. mysql, db2, firebird, etc and to switch the backend all you > need to do is change a line in artifact_aliases.properties. I'm > trying this out with Peter Petersson with the roller plugin we've > started in the plugins dir. That sounds like the right direction. This might get easier if we separate the datasource component from the actual database itself. I'm not sure about the roller plugin, but the Liferay datasource component includes not only the datasource but a derby database that is prepopulated with the Liferay schema. So, a side effect of installing the Liferay datasource plugin is that you get a new derby database under var/derby that's ready to roll. From an end user's perspective this makes it really easy to get a running portal server in Geronimo as a POC. But users looking for more configurability and optimization are not as well served. That becomes apparent as you read Hernan's new article. > Anyway, I think its generally better to have the "other project" > supply plugins for the databases they support rather than asking > users to create one themselves. Making the process easy... that > will be the challenge. I totally agree here as well. I think the main impediment right now is that setting up and maintaining a plugin repository (or even just a collection of plugins to be hosted elsewhere) requires some research and trial and error. We can help that situation by providing more examples and documentation, and by improving the overall design. I hope that Geronimo's own plugin repository will provide an example worth emulating. Best wishes, Paul --Apple-Mail-5--149689887 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
On Apr 4, 2007, at = 6:10 PM, David Jencks wrote:

What I'm = hoping for in the future for these kinds of situations is that there can = be plugins configured for each of several databases, e.g. mysql, db2, = firebird, etc and to switch the backend all you need to do is change a = line in artifact_aliases.properties.=A0 I'm trying this out with Peter = Petersson with the roller plugin we've started in the plugins = dir.

That sounds like the right = direction.=A0 This might get easier if we separate the datasource = component from the actual database itself.=A0 I'm not sure about the = roller plugin, but the Liferay datasource component includes not only = the datasource but a derby database that is prepopulated with the = Liferay schema.=A0 So, a side effect of installing the Liferay = datasource plugin is that you get a new derby database under var/derby = that's ready to roll.=A0 =46rom an end user's perspective this makes it = really easy to get a running portal server in Geronimo as a POC.=A0 But = users looking for more configurability and optimization are not as well = served.=A0 That becomes apparent as you read Hernan's new = article.

Anyway, I = think its generally better to have the "other project" supply plugins = for the databases they support rather than asking users to create one = themselves.=A0 Making the process easy... that will be the = challenge.

I totally agree here = as well.=A0 I think the main impediment right now is that setting up and = maintaining a plugin repository (or even just a collection of plugins to = be hosted elsewhere) requires some research and trial and error.=A0 =A0We = can help that situation by providing more examples and documentation, = and by improving the overall design.=A0 I hope that Geronimo's own = plugin repository will provide an example worth emulating.


Best = wishes,
Paul
= --Apple-Mail-5--149689887--