Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (herse.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:X-YMail-OSG:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:From:Subject:Date:To:X-Mailer;
  b=RwLcZ0IAi40dxaqDqJZO3+V2MSJpKNOweZ7B7AP+TOngpaiS8ssBO5dF/3PquOXnmmwZWq3otiHN2oJQ62s2LdyPCWn55/xXeoc2eTA7Jg/FzfCv8r2hbiD8vqCxIkktB8ImKomAN3Pbu3O0x0yXX4vVMCx56Tpro9g1+Xovdoo=
  ;
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <758EA8BD-17F0-4C02-9AA1-9A81EF989CCB@gmail.com>
References: <461401AB.8020505@gmail.com>
 <EBF8D8F0-650B-4162-9BCC-BEF9DCA62E06@gmail.com> <46141214.7070003@gmail.com>
 <758EA8BD-17F0-4C02-9AA1-9A81EF989CCB@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-10--151075468
Message-Id: <03B36D73-1CCF-4FE3-9992-1F1AE9C32F99@yahoo.com>
From: David Jencks <david_jencks@yahoo.com>
Subject: Re: Running portlets in Geronimo - Documentation
Date: Wed, 4 Apr 2007 15:10:19 -0700
To: user@geronimo.apache.org


--Apple-Mail-10--151075468
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On Apr 4, 2007, at 2:34 PM, Paul McMahan wrote:

> On Apr 4, 2007, at 5:01 PM, Hernan Cunico wrote:
>
>> A limitation of the data source creation wizard is that you cannot  
>> specify some of the values, more specifically all those that make  
>> the moduleId. Liferay plugin is specifically looking for a  
>> connection pool named *LiferayPool*  and with the following  
>> moduleId *liferay/liferay-pool/4.2.1/car*. If you use the console  
>> you'll get something like console.dbpool/LiferayPool/1.0/rar and  
>> installing the portal server plugin will fail.
>
> Hernan, you're exactly right.  I had forgotten about that  
> limitation of the data source wizard and how that the portal plugin  
> relies on the datasource plugin to use a certain module name.  The  
> original reason I put that dependency in place was to facilitate  
> the relationship between the plugins so that if you install portal  
> plugin it will automatically download and install the datasource  
> plugin.  Or you could deploy a customized datasource beforehand  
> (like the mysql one you provided instructions for) and the plugin  
> installer wouldn't try to replace it with the derby one.  The end  
> goal was to minimize the number of steps it takes new users to get  
> a working portal server, while still allowing more advanced users  
> to use an external database like mysql or DB2.
>
> At least that's how it used to work.  Now I believe the plugin  
> catalog lists the datasource plugin as a "prerequisite" of the  
> portal plugin instead of just a "dependency", so the plugin  
> installer lists the portal plugin as unavailable until you have  
> installed the datasource plugin.  The Liferay team maintains the  
> catalog so that may be how they prefer things.  Or they might want  
> to refine that part of their plugin catalog when we look into  
> updating it for Geronimo's upcoming 1.2 release.

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.

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.

thanks
david jencks

>
> Best wishes,
> Paul


--Apple-Mail-10--151075468
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><BR><DIV><DIV>On Apr 4, 2007, at =
2:34 PM, Paul McMahan wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV><DIV>On=
 Apr 4, 2007, at 5:01 PM, Hernan Cunico wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">A limitation of the data source creation wizard is =
that you cannot specify some of the values, more specifically all those =
that make the moduleId. Liferay plugin is specifically looking for a =
connection pool named *LiferayPool*<SPAN class=3D"Apple-converted-space">=A0=
 </SPAN>and with the following moduleId =
*liferay/liferay-pool/4.2.1/car*. If you use the console you'll get =
something like console.dbpool/LiferayPool/1.0/rar and installing the =
portal server plugin will fail.</FONT></DIV> =
</BLOCKQUOTE></DIV><BR><DIV>Hernan, you're exactly right.=A0 I had =
forgotten about that limitation of the data source wizard and how that =
the portal plugin relies on the datasource plugin to use a certain =
module name.=A0 The original reason I put that dependency in place was =
to facilitate the relationship between the plugins so that if you =
install portal plugin it will automatically download and install the =
datasource plugin.=A0 Or you could deploy a customized datasource =
beforehand (like the mysql one you provided instructions for) and the =
plugin installer wouldn't try to replace it with the derby one.=A0 The =
end goal was to minimize the number of steps it takes new users to get a =
working portal server, while still allowing more advanced users to use =
an external database like mysql or DB2.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>At least that's how it used =
to work.=A0 Now I believe the plugin catalog lists the datasource plugin =
as a "prerequisite" of the portal plugin instead of just a "dependency", =
so the plugin installer lists the portal plugin as unavailable until you =
have installed the datasource plugin.=A0 The Liferay team maintains the =
catalog so that may be how they prefer things.=A0 Or they might want to =
refine that part of their plugin catalog when we look into updating it =
for Geronimo's upcoming 1.2 release.</DIV></BLOCKQUOTE><DIV><BR =
class=3D"khtml-block-placeholder"></DIV>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.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>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.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>thanks</DIV><DIV>david =
jencks</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><BLOCKQUOTE =
type=3D"cite"><DIV><BR class=3D"khtml-block-placeholder"></DIV><DIV>Best =
wishes,</DIV><DIV>Paul</DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>=

--Apple-Mail-10--151075468--