Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 82025 invoked from network); 23 Aug 2010 19:05:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Aug 2010 19:05:06 -0000 Received: (qmail 69806 invoked by uid 500); 23 Aug 2010 19:05:06 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 69784 invoked by uid 500); 23 Aug 2010 19:05:06 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 69776 invoked by uid 99); 23 Aug 2010 19:05:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Aug 2010 19:05:06 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of esjewett@gmail.com designates 209.85.216.175 as permitted sender) Received: from [209.85.216.175] (HELO mail-qy0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Aug 2010 19:04:59 +0000 Received: by qyk8 with SMTP id 8so3188233qyk.6 for ; Mon, 23 Aug 2010 12:04:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=6fKY2xOX3n8mGbQxJgC0Vk6BVXAepv5nQgRVVYK/P1s=; b=ioSGMTEYlcd5w5DllWSf9dteoCAfjrrIptnl/Mdj9y8yDA1K3OArLbIaK9IvjBOZjD tOYbX1sAy/uSNlqkaNVXplU4GdGiwZXiLnJPw+7yqfOna0NyOGO99F6mM8GxxvRVPyaU HRdvUi/mPmI7jCtj9V00STOyviLLS8eLnZuw0= 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=vophj9FFmNSsQAIgkOVHLS9+2MxKZUaGUYBl/nS3wcprjUlbKduLJspOy3TvBOR9WM GlXgcFwdBkKbEDapIayiljujUCIHfvN3d1mn7e1dZj8JTSgORY3kjCTutSN2QO/wCSCp /OK0P+nOV991lyMtvc9C/umT+cQm4d0Bv2C3Q= MIME-Version: 1.0 Received: by 10.229.96.84 with SMTP id g20mr2716485qcn.47.1282590278734; Mon, 23 Aug 2010 12:04:38 -0700 (PDT) Received: by 10.229.95.69 with HTTP; Mon, 23 Aug 2010 12:04:38 -0700 (PDT) In-Reply-To: References: <1402376990-1282570507-cardhu_decombobulator_blackberry.rim.net-1467022559-@bda188.bisx.produk.on.blackberry> Date: Mon, 23 Aug 2010 14:04:38 -0500 Message-ID: Subject: Re: Stax deployment with new code - despite bugs From: Ethan Jewett To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org I believe that the CSS trick was what caused issue ESME-231 :-) What we really need to do is make it so that we can put the snippets in the right order in the HTML so that we don't have to do any crazy tricks. As far as I can tell (again, have not looked at it carefully), the bug is that the ordering of the HTML matters. That is usually a no-no for exactly this reason. So, maybe we shouldn't close this issue, contrary to my last email. I'll leave it open for now. Can you update with all the requirements (correct ordering, footer works properly, and pool selection works properly)? I would do it, but I'm on my way out the door. Thanks, Ethan On Mon, Aug 23, 2010 at 1:59 PM, Richard Hirsch wro= te: > This is a bug. =A0The selector box has to be on the top of the page. I > used a CSS trick to get it to stay there. > > Maybe you should revert back to the version before your initial change? > > D. > > On Mon, Aug 23, 2010 at 8:54 PM, Ethan Jewett wrote: >> I've applied this patch minus the pubsubhubbub stuff that was in >> there. It looks to me like it is working, though the streams selection >> interface has moved to the bottom of the page now, so that may be >> undesirable. >> >> I'm still not sure why the order matters here. Seems to me like a bug ..= .. >> >> Ethan >> >> On Mon, Aug 23, 2010 at 8:35 AM, =A0 wrote: >>> That's what I did unknowingly! :) >>> >>> Imtiaz >>> >>> Imtiaz Ahmed H E >>> Cell +91.98452 84561 >>> Bangalore, India >>> >>> >>> -----Original Message----- >>> From: Ethan Jewett >>> Date: Mon, 23 Aug 2010 08:29:07 >>> To: >>> Reply-To: esme-dev@incubator.apache.org >>> Subject: Re: Stax deployment with new code - despite bugs >>> >>> Hi Imtiaz, >>> >>> My patch modified two files: style.css and streams.html. >>> >>> If you backed out the changes to streams.html only and left style.css >>> as it was before, then I think we should be OK. I'll retest with the >>> patch later today. >>> >>> Thanks for the patch! >>> >>> Ethan >>> >>> On Mon, Aug 23, 2010 at 3:09 AM, Imtiaz Ahmed H E = wrote: >>>> Let me elaborate... >>>> >>>> The last deployment on Stax without this bug according to Dick was on = July >>>> 12th. >>>> >>>> Ethan made a change and checked in 17th July which has caused this bug= . >>>> >>>> I simply undid his checkin; re the revert to 942677 which is the 10th = May >>>> checkin. >>>> >>>> Reference: >>>> http://svn.apache.org/viewvc/incubator/esme/trunk/server/src/main/weba= pp/info_view/streams.html?view=3Dlog >>>> >>>> Imtiaz >>>> >>>> ----- Original Message ----- From: "Imtiaz Ahmed H E" >>>> To: >>>> Sent: Monday, August 23, 2010 1:14 PM >>>> Subject: Re: Stax deployment with new code - despite bugs >>>> >>>> >>>>> Find attached to the Jira autologically named file >>>>> ESmeJira259PatchByRevertingTo_r942677_Reopens231Presumably.diff =A0:-= ) >>>>> >>>>> Somebody now needs to re-look at 231 :( >>>>> >>>>> Imtiaz >>>>> >>>>> ----- Original Message ----- From: "Richard Hirsch" >>>>> >>>>> To: >>>>> Sent: Sunday, August 22, 2010 12:35 PM >>>>> Subject: Re: Stax deployment with new code - despite bugs >>>>> >>>>> >>>>> The last stax deplyoment =A0( >>>>> http://esmecloudserverapache.DickHirsch.staxapps.net) was on Jul 12, >>>>> 2010. >>>>> >>>>> D. >>>>> >>>>> On Sun, Aug 22, 2010 at 8:54 AM, Imtiaz Ahmed H E >>>>> wrote: >>>>>> >>>>>> In that case, it will help to locate the problem if you can tell me = the >>>>>> date >>>>>> of that deployment so that I can check the subsequent check-ins to s= ee >>>>>> what >>>>>> happened. >>>>>> >>>>>> I myself will not be looking at the Stax deployment. >>>>>> >>>>>> Imtiaz >>>>>> >>>>>> ----- Original Message ----- From: "Richard Hirsch" >>>>>> >>>>>> To: >>>>>> Sent: Sunday, August 22, 2010 12:13 PM >>>>>> Subject: Re: Stax deployment with new code - despite bugs >>>>>> >>>>>> >>>>>>> If you take a look at the current deployment on stax, you will see >>>>>>> that it works there. >>>>>>> >>>>>>> D. >>>>>>> >>>>>>> On Sun, Aug 22, 2010 at 7:02 AM, Imtiaz Ahmed H E >>>>>>> wrote: >>>>>>>> >>>>>>>> Dick, >>>>>>>> >>>>>>>> Following your earlier mail saying you find new bugs on your retur= n, >>>>>>>> this >>>>>>>> morning I started investigating ESME-259 and it doesn't look like = it >>>>>>>> was >>>>>>>> working at any time. Not too sure. Still figuring it out. Will hav= e it >>>>>>>> done >>>>>>>> asap. >>>>>>>> >>>>>>>> Imtiaz >>>>>>>> >>>>>>>> ----- Original Message ----- From: "Richard Hirsch" >>>>>>>> >>>>>>>> To: >>>>>>>> Sent: Sunday, August 22, 2010 10:04 AM >>>>>>>> Subject: Stax deployment with new code - despite bugs >>>>>>>> >>>>>>>> >>>>>>>>> As I work towards the next release, I've found a new bugs in the >>>>>>>>> current source that don't exist on stax (For example, >>>>>>>>> https://issues.apache.org/jira/browse/ESME-259). I'd still like t= o >>>>>>>>> deploy it on stax. >>>>>>>>> >>>>>>>>> Does anyone have a problem with that? >>>>>>>>> >>>>>>>>> D. >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >