Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of c1vamsi1c@gmail.com designates
 64.233.182.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=XC3zV8R4BwGGdUrByx0mvtopuloSam8QU7bz7v3/TgmAtDL7DSWnHe4oJ/C3Qt/AsMz5RsN1F1HM6tFkHW0jP6za9TzH5/RQW3+ke6E6r+D1knZOtDkB/CUOjpZhiiutuqxE5QbD3iIESSVnmG10yRwHHEc6C/rPt8+TN1Ta13g=
Message-ID: <22d56c4d0611071103h11cc0d6dpd95a4318b6ec2946@mail.gmail.com>
Date: Wed, 8 Nov 2006 00:33:19 +0530
From: "Vamsavardhana Reddy" <c1vamsi1c@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: database pool portlet needs a big port from 1.1 branch to trunk
In-Reply-To: <21df75940611070936t4e1a2d6u70fb2c54bda3a1e3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_12922_33352002.1162926199894"
References: <638C2245-DC02-4B09-9D93-FB233FDB4C77@yahoo.com>
	 <21df75940611070936t4e1a2d6u70fb2c54bda3a1e3@mail.gmail.com>

------=_Part_12922_33352002.1162926199894
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You are welcome Paul.  And thank you for taking care of GERONIMO-2553
promptly.  I have been addressing the JIRA's due to be fixed in 1.1.2 and
1.1.x.  and when I am trying to apply those fixes to trunk, I am finding
that some very basic things are failing in the Admin Console.  Admin Console
needs to be tested because some of the other changes seems to have broken
some portlets.  Though it may not be possible to test everything thoroughly
after applying a fix, a minimum amount of testing should be done before
committing the fix to svn.  In the past two days, I have noticed problems
with SecurityRealm and DatabasePool portlets.  There are still some problems
with SecurityRealm portlet.  Testing the fixes is a long process.  Past two
days, I have noticed that building the server to test a fix is taking 3
times the time spent on the actual fix :o(.  We need some improvement to the
build process.

--vamsi

On 11/7/06, Paul McMahan <paulmcmahan@gmail.com> wrote:
>
> David,  I ported the change that externalizes the database driver info
> into GBeans.  Next I plan to look at the list of pending merges in
> all_changes.log and move those forward if necessary.  Then I'll take
> an overall look at the console to see what else might have been left
> behind or just needs some tweaking :-)    Vamsi has been helping look
> into this too (thanks Vamsi!).
>
> Best wishes,
> Paul
>
> On 11/7/06, David Jencks <david_jencks@yahoo.com > wrote:
> > The database pool portlet code is dramatically different and better
> > in the 1.1 branch than in trunk.  I've been hoping Aaron (original
> > author of the improvements) would find some time to port these but I
> > see some changes going into  trunk that do not look like a forward port.
> >
> > Does anyone have the time and/or interest to study this and merge the
> > changes?
> >
> > thanks
> > david jencks
> >
> >
>

------=_Part_12922_33352002.1162926199894
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You are welcome Paul.&nbsp; And thank you for taking care of
GERONIMO-2553 promptly.&nbsp; I have been addressing the JIRA's due to
be fixed in 1.1.2 and 1.1.x.&nbsp; and when I am trying to apply those
fixes to trunk, I am finding that some very basic things are failing in
the Admin Console.&nbsp; Admin Console needs to be tested because some
of the other changes seems to have broken some portlets.&nbsp; Though
it may not be possible to test everything thoroughly after applying a
fix, a minimum amount of testing should be done before committing the
fix to svn.&nbsp; In the past two days, I have noticed problems with
SecurityRealm and DatabasePool portlets.&nbsp; There are still some
problems with SecurityRealm portlet.&nbsp; Testing the fixes is a long
process.&nbsp; Past two days, I have noticed that building the server
to test a fix is taking 3 times the time spent on the actual fix
:o(.&nbsp; We need some improvement to the build process.<br>
<br>
--vamsi<br><br><div><span class="gmail_quote">On 11/7/06, <b class="gmail_sendername">Paul McMahan</b> &lt;<a href="mailto:paulmcmahan@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">paulmcmahan@gmail.com
</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
David,&nbsp;&nbsp;I ported the change that externalizes the database driver info<br>into GBeans.&nbsp;&nbsp;Next I plan to look at the list of pending merges in<br>all_changes.log and move those forward if necessary.&nbsp;&nbsp;Then I'll take<br>an overall look at the console to see what else might have been left
<br>behind or just needs some tweaking :-)&nbsp;&nbsp;&nbsp;&nbsp;Vamsi has been helping look<br>into this too (thanks Vamsi!).<br><br>Best wishes,<br>Paul<br><br>On 11/7/06, David Jencks &lt;<a href="mailto:david_jencks@yahoo.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
david_jencks@yahoo.com
</a>&gt; wrote:<br>&gt; The database pool portlet code is dramatically different and better<br>&gt; in the 1.1 branch than in trunk.&nbsp;&nbsp;I've been hoping Aaron (original<br>&gt; author of the improvements) would find some time to port these but I
<br>&gt; see some changes going into&nbsp;&nbsp;trunk that do not look like a forward port.<br>&gt;<br>&gt; Does anyone have the time and/or interest to study this and merge the<br>&gt; changes?<br>&gt;<br>&gt; thanks<br>&gt; david jencks
<br>&gt;<br>&gt;<br></blockquote></div><br>

------=_Part_12922_33352002.1162926199894--