From jmurphy@example.com Thu Apr 01 13:49:02 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 58939 invoked from network); 1 Apr 2010 13:49:02 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 1 Apr 2010 13:49:02 -0000 Received: (qmail 93336 invoked by uid 500); 1 Apr 2010 13:49:02 -0000 Delivered-To: jmurphy@example.com Received: (qmail 93301 invoked by uid 500); 1 Apr 2010 13:49:01 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 93293 invoked by uid 99); 1 Apr 2010 13:49:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 13:49:01 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=AWL,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO smtp.rivulet.ca) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 13:48:54 +0000 Received: from [83.161.120.155] (unknown [83.161.120.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.rivulet.ca (Postfix) with ESMTPSA id 415FB647FA for <jmurphy@example.com>; Thu, 1 Apr 2010 09:48:30 -0400 (EDT) Message-ID: <jmurphy@example.com> Date: Thu, 01 Apr 2010 09:48:31 -0400 From: Michael O'Cleirigh <jmurphy@example.com> User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:83.161.120.155) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: jmurphy@example.com Subject: WicketStuff Teamcity can't access the sourceforge subversion repository Content-Type: multipart/alternative; boundary="------------070405030406090402090108" --------------070405030406090402090108 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello, Recently there has been some initiative in organizing more WicketStuff core releases and changes have been going into the sourceforge subversion repository for that effect. But there is a problem with Teamcity not being able to access the wicketstuff repository which prevents the updated artifacts being built and distributed into the maven snapshot repository. I like to only checkout the specific submodules I work on and have m2eclipse resolve the parent from the snapshot repository; but that approach doesn't work when the snapshots are not being created. I searched the dev list archive and there was a problem like this in the past (Re: TeamCity on wicketstuff.org from November 29 2008). Here is a link to the build log with the '//org.tmatesoft.svn.core.SVNException: svn: connection refused by the server'// error: http://wicketstuff.org/teamcity/viewLog.html?buildId=5903&tab=buildResultsDiv&buildTypeId=bt35 It feels like the build server might be blacklisted in some way by sourceforge; although it could be something else. Does anyone know what was done before or have a contact from that time which could be used to get teamcity talking subversion again? Thanks, Mike --------------070405030406090402090108-- From jmurphy@example.com Thu Apr 01 16:57:02 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 26008 invoked from network); 1 Apr 2010 16:57:01 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 1 Apr 2010 16:57:01 -0000 Received: (qmail 49671 invoked by uid 500); 1 Apr 2010 16:57:01 -0000 Delivered-To: jmurphy@example.com Received: (qmail 49648 invoked by uid 500); 1 Apr 2010 16:57:01 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 49640 invoked by uid 99); 1 Apr 2010 16:57:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 16:57:01 +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 jmurphy@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-yw0-f191.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 16:56:55 +0000 Received: by ywh29 with SMTP id 29so2133512ywh.14 for <jmurphy@example.com>; Thu, 01 Apr 2010 09:56:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type :content-transfer-encoding; bh=R9ILhzknTh6F5I3KU/mmVNHdxCV5OFxBsjQm7SBoMt8=; b=f09Co98sD5Kto+eHjKr/TPHiV1c+jQZ6aTNgFAZzUtwht/N9ZQJl7B855Sv8uTETi5 eQKrkloSd+zCE3GQYH+LPTsZ0UREpffMYdWG4sXmMbXcpqjIB1rQ+iie36gfIL0AI8cX e52caeu8o845tj1ov+ZZIIIsq82v5MKTlf7e0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=MiN/uvTPCvkp2RoNZZK5RL0KSHWBDinkJFgbal5v9ObzcboCUPuVV4BvOw2nDwmqfy H3ujY0nNPILIhLjC8JpdhhRv4xgXR0OdzL4fOzYuP23gTqfkQ27BCYEftjPTjOeRBSMq 6GVlkhrvk1b1Anf56iQl4r3gJQTMUotWsX4bQ= MIME-Version: 1.0 Received: by 83.161.120.155 with HTTP; Thu, 1 Apr 2010 09:51:26 -0700 (PDT) In-Reply-To: <jmurphy@example.com> References: <jmurphy@example.com> From: Igor Vaynberg <jmurphy@example.com> Date: Thu, 1 Apr 2010 09:51:26 -0700 Received: by 83.161.120.155 with SMTP id v11mr2752065anl.18.1270140994213; Thu, 01 Apr 2010 09:56:34 -0700 (PDT) Message-ID: <jmurphy@example.com> Subject: Re: WicketStuff Teamcity can't access the sourceforge subversion repository To: jmurphy@example.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org sf.net keeps banning our TC instance because they think it access svn too often. nothing we can do about it. i think nino filed a ticket with them that never got resolved. -igor On Thu, Apr 1, 2010 at 6:48 AM, Michael O'Cleirigh <jmurphy@example.com> wrote: > Hello, > > Recently there has been some initiative in organizing more WicketStuff co= re > releases and changes have been going into the sourceforge subversion > repository for that effect. > > But there is a problem with Teamcity not being able to access the > wicketstuff repository which prevents the updated artifacts being built a= nd > distributed into the maven snapshot repository. =A0I like to only checkou= t the > specific submodules I work on and have m2eclipse resolve the parent from = the > snapshot repository; but that approach doesn't work when the snapshots ar= e > not being created. > > I searched the dev list archive and there was a problem like this in the > past (Re: TeamCity on wicketstuff.org from November 29 2008). > > Here is a link to the build log with the > '//org.tmatesoft.svn.core.SVNException: svn: connection refused by the > server'// =A0error: > http://wicketstuff.org/teamcity/viewLog.html?buildId=3D5903&tab=3DbuildRe= sultsDiv&buildTypeId=3Dbt35 > > It feels like the build server might be blacklisted in some way by > sourceforge; although it could be something else. > > Does anyone know what was done before or have a contact from that time wh= ich > could be used to get teamcity talking subversion again? > > Thanks, > > Mike > > > > > From jmurphy@example.com Sun Apr 04 08:14:10 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 55173 invoked from network); 4 Apr 2010 08:14:10 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 4 Apr 2010 08:14:10 -0000 Received: (qmail 89121 invoked by uid 500); 4 Apr 2010 08:14:10 -0000 Delivered-To: jmurphy@example.com Received: (qmail 88960 invoked by uid 500); 4 Apr 2010 08:14:08 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 88947 invoked by uid 99); 4 Apr 2010 08:14:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Apr 2010 08:14:07 +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 jmurphy@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-fx0-f212.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Apr 2010 08:14:01 +0000 Received: by fxm4 with SMTP id 4so1469504fxm.6 for <jmurphy@example.com>; Sun, 04 Apr 2010 01:13:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type :content-transfer-encoding; bh=S4u4xtU3PdyFPK7GjrMmfFTpZ4KX3TP13Z18Pd3l6+I=; b=hDqJ3cpNflm59lZ46sJ44hzY+8FqtlWHENHq+qWgOx8g8v0i5gMgOxkZLbQufDdRXy OQtFt7iVOMH3BVe4m93sKiNyvAmNRBe0Ps36wTaXADc1crB9Auale3E95WD+v0/MddYK pMkxGEfOLKuwLgq2vA4DF33bpBKgwE22ElaXg= 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=unA+RPtpiKcFyCf/2tdD/prhCiT+WDN3GW8hjcmwnBelmelaYoAswaLmNkL8LPB94c VlB+ZyYl/URgA6bLTj5tsG3yhBhSYy/uVFw2MziVlxB4QQszOG6r4PsXR0YqBEBMd2f8 djnAomiTQ7OjsmwFMTC9+V9tug9tjjvakLk1k= MIME-Version: 1.0 Received: by 83.161.120.155 with HTTP; Sun, 4 Apr 2010 01:13:40 -0700 (PDT) In-Reply-To: <jmurphy@example.com> References: <jmurphy@example.com> <jmurphy@example.com> Date: Sun, 4 Apr 2010 10:13:40 +0200 Received: by 83.161.120.155 with SMTP id p20mr427754hbh.7.1270368820656; Sun, 04 Apr 2010 01:13:40 -0700 (PDT) Message-ID: <jmurphy@example.com> Subject: Re: WicketStuff Teamcity can't access the sourceforge subversion repository From: nino martinez wael <jmurphy@example.com> To: jmurphy@example.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Correct as always. I think Sf were convinced that it was not their problem or something. We actually switched from Bamboo to TeamCity for that reason.. I also created a separate project on google called wicketstuff, but we never could agree on using that instead of sf. regards Nino 2010/4/1 Igor Vaynberg <jmurphy@example.com>: > sf.net keeps banning our TC instance because they think it access svn > too often. nothing we can do about it. i think nino filed a ticket > with them that never got resolved. > > -igor > > On Thu, Apr 1, 2010 at 6:48 AM, Michael O'Cleirigh > <jmurphy@example.com> wrote: >> Hello, >> >> Recently there has been some initiative in organizing more WicketStuff c= ore >> releases and changes have been going into the sourceforge subversion >> repository for that effect. >> >> But there is a problem with Teamcity not being able to access the >> wicketstuff repository which prevents the updated artifacts being built = and >> distributed into the maven snapshot repository. =A0I like to only checko= ut the >> specific submodules I work on and have m2eclipse resolve the parent from= the >> snapshot repository; but that approach doesn't work when the snapshots a= re >> not being created. >> >> I searched the dev list archive and there was a problem like this in the >> past (Re: TeamCity on wicketstuff.org from November 29 2008). >> >> Here is a link to the build log with the >> '//org.tmatesoft.svn.core.SVNException: svn: connection refused by the >> server'// =A0error: >> http://wicketstuff.org/teamcity/viewLog.html?buildId=3D5903&tab=3DbuildR= esultsDiv&buildTypeId=3Dbt35 >> >> It feels like the build server might be blacklisted in some way by >> sourceforge; although it could be something else. >> >> Does anyone know what was done before or have a contact from that time w= hich >> could be used to get teamcity talking subversion again? >> >> Thanks, >> >> Mike >> >> >> >> >> > From jmurphy@example.com Sun Apr 04 11:53:07 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 72449 invoked from network); 4 Apr 2010 11:53:06 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 4 Apr 2010 11:53:06 -0000 Received: (qmail 71187 invoked by uid 500); 4 Apr 2010 11:53:06 -0000 Delivered-To: jmurphy@example.com Received: (qmail 71148 invoked by uid 500); 4 Apr 2010 11:53:06 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 71138 invoked by uid 99); 4 Apr 2010 11:53:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Apr 2010 11:53:06 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=AWL,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO qw-out-1920.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Apr 2010 11:53:01 +0000 Received: by qw-out-1920.google.com with SMTP id 9so1268391qwj.2 for <jmurphy@example.com>; Sun, 04 Apr 2010 04:52:40 -0700 (PDT) MIME-Version: 1.0 Received: by 83.161.120.155 with HTTP; Sun, 4 Apr 2010 04:52:20 -0700 (PDT) In-Reply-To: <jmurphy@example.com> References: <jmurphy@example.com> <jmurphy@example.com> <jmurphy@example.com> From: James Carman <jmurphy@example.com> Date: Sun, 4 Apr 2010 07:52:20 -0400 Received: by 83.161.120.155 with SMTP id if12mr582661qcb.17.1270381960429; Sun, 04 Apr 2010 04:52:40 -0700 (PDT) Message-ID: <jmurphy@example.com> Subject: Re: WicketStuff Teamcity can't access the sourceforge subversion repository To: jmurphy@example.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable It might be worth putting a simple test project out there on google to see if we get banned there too. On Sun, Apr 4, 2010 at 4:13 AM, nino martinez wael <jmurphy@example.com> wrote: > Correct as always. > > I think Sf were convinced that it was not their problem or something. > We actually switched from Bamboo to TeamCity for that reason.. I also > created a separate project on google called wicketstuff, but we never > could agree on using that instead of sf. > > regards Nino > > 2010/4/1 Igor Vaynberg <jmurphy@example.com>: >> sf.net keeps banning our TC instance because they think it access svn >> too often. nothing we can do about it. i think nino filed a ticket >> with them that never got resolved. >> >> -igor >> >> On Thu, Apr 1, 2010 at 6:48 AM, Michael O'Cleirigh >> <jmurphy@example.com> wrote: >>> Hello, >>> >>> Recently there has been some initiative in organizing more WicketStuff = core >>> releases and changes have been going into the sourceforge subversion >>> repository for that effect. >>> >>> But there is a problem with Teamcity not being able to access the >>> wicketstuff repository which prevents the updated artifacts being built= and >>> distributed into the maven snapshot repository. =A0I like to only check= out the >>> specific submodules I work on and have m2eclipse resolve the parent fro= m the >>> snapshot repository; but that approach doesn't work when the snapshots = are >>> not being created. >>> >>> I searched the dev list archive and there was a problem like this in th= e >>> past (Re: TeamCity on wicketstuff.org from November 29 2008). >>> >>> Here is a link to the build log with the >>> '//org.tmatesoft.svn.core.SVNException: svn: connection refused by the >>> server'// =A0error: >>> http://wicketstuff.org/teamcity/viewLog.html?buildId=3D5903&tab=3Dbuild= ResultsDiv&buildTypeId=3Dbt35 >>> >>> It feels like the build server might be blacklisted in some way by >>> sourceforge; although it could be something else. >>> >>> Does anyone know what was done before or have a contact from that time = which >>> could be used to get teamcity talking subversion again? >>> >>> Thanks, >>> >>> Mike >>> >>> >>> >>> >>> >> > From jmurphy@example.com Tue Apr 06 08:15:37 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 32712 invoked from network); 6 Apr 2010 08:15:37 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 6 Apr 2010 08:15:37 -0000 Received: (qmail 30867 invoked by uid 500); 6 Apr 2010 08:15:37 -0000 Delivered-To: jmurphy@example.com Received: (qmail 30707 invoked by uid 500); 6 Apr 2010 08:15:35 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 30697 invoked by uid 99); 6 Apr 2010 08:15:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 08:15:34 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jmurphy@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO omega.fullsix.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 08:15:26 +0000 Received: from perseus.f6.fr (perseus.f6.fr [83.161.120.155]) by omega.fullsix.com (Postfix) with SMTP id CE2006037 for <jmurphy@example.com>; Tue, 6 Apr 2010 10:15:05 +0200 (CEST) Received: from omega.fullsix.com ([83.161.120.155]) by localhost (omega.f6.fr [83.161.120.155]) (amavisd-new, port 10024) with LMTP id 7uWT5UVSPsCL for <jmurphy@example.com>; Tue, 6 Apr 2010 10:15:04 +0200 (CEST) Received: from hal.f6.fr (darkstar2.fullsix.com [83.161.120.155]) (Authenticated sender: bruyeron) by omega.fullsix.com (Postfix) with ESMTPA id 09D6A6013 for <jmurphy@example.com>; Tue, 6 Apr 2010 10:15:04 +0200 (CEST) Message-ID: <jmurphy@example.com> Date: Tue, 06 Apr 2010 10:15:03 +0200 From: Renaud Bruyeron <jmurphy@example.com> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:83.161.120.155) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: jmurphy@example.com Subject: Re: WicketStuff Teamcity can't access the sourceforge subversion repository References: <jmurphy@example.com> <jmurphy@example.com> <jmurphy@example.com> <jmurphy@example.com> In-Reply-To: <jmurphy@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Has anyone considered github for wicketstuff? it looks like the perfect place for something like wicketstuff Renaud On 4/4/10 1:52 PM, James Carman wrote: > It might be worth putting a simple test project out there on google to > see if we get banned there too. > > On Sun, Apr 4, 2010 at 4:13 AM, nino martinez wael > <jmurphy@example.com> wrote: > >> Correct as always. >> >> I think Sf were convinced that it was not their problem or something. >> We actually switched from Bamboo to TeamCity for that reason.. I also >> created a separate project on google called wicketstuff, but we never >> could agree on using that instead of sf. >> >> regards Nino >> >> 2010/4/1 Igor Vaynberg<jmurphy@example.com>: >> >>> sf.net keeps banning our TC instance because they think it access svn >>> too often. nothing we can do about it. i think nino filed a ticket >>> with them that never got resolved. >>> >>> -igor >>> >>> On Thu, Apr 1, 2010 at 6:48 AM, Michael O'Cleirigh >>> <jmurphy@example.com> wrote: >>> >>>> Hello, >>>> >>>> Recently there has been some initiative in organizing more WicketStuff core >>>> releases and changes have been going into the sourceforge subversion >>>> repository for that effect. >>>> >>>> But there is a problem with Teamcity not being able to access the >>>> wicketstuff repository which prevents the updated artifacts being built and >>>> distributed into the maven snapshot repository. I like to only checkout the >>>> specific submodules I work on and have m2eclipse resolve the parent from the >>>> snapshot repository; but that approach doesn't work when the snapshots are >>>> not being created. >>>> >>>> I searched the dev list archive and there was a problem like this in the >>>> past (Re: TeamCity on wicketstuff.org from November 29 2008). >>>> >>>> Here is a link to the build log with the >>>> '//org.tmatesoft.svn.core.SVNException: svn: connection refused by the >>>> server'// error: >>>> http://wicketstuff.org/teamcity/viewLog.html?buildId=5903&tab=buildResultsDiv&buildTypeId=bt35 >>>> >>>> It feels like the build server might be blacklisted in some way by >>>> sourceforge; although it could be something else. >>>> >>>> Does anyone know what was done before or have a contact from that time which >>>> could be used to get teamcity talking subversion again? >>>> >>>> Thanks, >>>> >>>> Mike >>>> >>>> >>>> >>>> >>>> >>>> >>> >> -- Renaud Bruyeron - CTO - FullSIX France 402.955.5320 From jmurphy@example.com Tue Apr 06 13:33:53 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 8295 invoked from network); 6 Apr 2010 13:33:53 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 6 Apr 2010 13:33:53 -0000 Received: (qmail 42988 invoked by uid 500); 6 Apr 2010 13:33:52 -0000 Delivered-To: jmurphy@example.com Received: (qmail 42942 invoked by uid 500); 6 Apr 2010 13:33:51 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 42934 invoked by uid 99); 6 Apr 2010 13:33:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 13:33:51 +0000 X-ASF-Spam-Status: No, hits=1.1 required=10.0 tests=AWL,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO nl-mail01.planon-fm.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 13:33:45 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAD58C.1FAF443E" Subject: Disable PageMap? Date: Tue, 6 Apr 2010 15:21:52 +0200 Message-ID: <jmurphy@example.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Disable PageMap? Thread-Index: AcrVjB8H9lb6mU7dT3e0Fzra11/a8Q== From: "Elger van Boxtel" <jmurphy@example.com> To: <jmurphy@example.com> ------_=_NextPart_001_01CAD58C.1FAF443E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Currently, pages are stored in a PageMap for each session when the user clicks the browser refresh button.=20 In our application pages can grow quite quite big (sometimes even up to 40MB). As you will understand, sessions can grow exponentially when storing one or more pages and will cause trouble with mulitple users over time. We've looked into the possibility of not storing the pages at all, but this did not seem to work as Wicket expects a page to be registered in the PageMap.=20 What we did so far is minimizing the number of pages stored in session: - we disabled versioning (org.apache.wicket.settings.IPageSettings.setVersionPagesByDefault) - we set max page maps to 1 (org.apache.wicket.settings.ISessionSettings.setMaxPageMaps) - we use LeastRecentlyAccessedEvictionStrategy(1) now, this evicts all older pages and one leaves 1 page (org.apache.wicket.settings.ISessionSettings.setPageMapEvictionStrategy) Does anyone know if we can disable statefull pages being stored in the session after a refresh or disable this functionality completely? Thanks in advance, Elger ------_=_NextPart_001_01CAD58C.1FAF443E-- From jmurphy@example.com Tue Apr 06 20:16:19 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 17727 invoked from network); 6 Apr 2010 20:16:19 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 6 Apr 2010 20:16:19 -0000 Received: (qmail 28586 invoked by uid 500); 6 Apr 2010 20:16:19 -0000 Delivered-To: jmurphy@example.com Received: (qmail 28543 invoked by uid 500); 6 Apr 2010 20:16:18 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 28535 invoked by uid 99); 6 Apr 2010 20:16:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 20:16:18 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO mail-gw0-f45.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 20:16:12 +0000 Received: by gwaa18 with SMTP id a18so104704gwa.32 for <jmurphy@example.com>; Tue, 06 Apr 2010 13:15:51 -0700 (PDT) MIME-Version: 1.0 Received: by 83.161.120.155 with HTTP; Tue, 6 Apr 2010 13:15:50 -0700 (PDT) In-Reply-To: <jmurphy@example.com> References: <jmurphy@example.com> Date: Tue, 6 Apr 2010 15:15:50 -0500 Received: by 83.161.120.155 with SMTP id r31mr8491138ybc.315.1270584950860; Tue, 06 Apr 2010 13:15:50 -0700 (PDT) Message-ID: <jmurphy@example.com> Subject: Re: Disable PageMap? From: Jeremy Thomerson <jmurphy@example.com> To: jmurphy@example.com Content-Type: multipart/alternative; boundary=000e0cd6d014a72d0b0483971c3c X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd6d014a72d0b0483971c3c Content-Type: text/plain; charset=ISO-8859-1 If your pages are 40MB the problem is not the PageMap - it's that you're doing something wrong with the pages - something that needs to be fixed ASAP. Most likely you are holding collections of data directly in the page instead of using models. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Apr 6, 2010 at 8:21 AM, Elger van Boxtel <jmurphy@example.com>wrote: > Hi, > > Currently, pages are stored in a PageMap for each session when the user > clicks the browser refresh button. > > In our application pages can grow quite quite big (sometimes even up to > 40MB). As you will understand, sessions can grow exponentially when > storing one or more pages and will cause trouble with mulitple users > over time. > > We've looked into the possibility of not storing the pages at all, but > this did not seem to work as Wicket expects a page to be registered in > the PageMap. > > What we did so far is minimizing the number of pages stored in session: > - we disabled versioning > (org.apache.wicket.settings.IPageSettings.setVersionPagesByDefault) > - we set max page maps to 1 > (org.apache.wicket.settings.ISessionSettings.setMaxPageMaps) > - we use LeastRecentlyAccessedEvictionStrategy(1) now, this evicts all > older pages and one leaves 1 page > (org.apache.wicket.settings.ISessionSettings.setPageMapEvictionStrategy) > > Does anyone know if we can disable statefull pages being stored in the > session after a refresh or disable this functionality completely? > > Thanks in advance, > > Elger > > --000e0cd6d014a72d0b0483971c3c-- From jmurphy@example.com Thu Apr 08 08:39:31 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 77919 invoked from network); 8 Apr 2010 08:39:31 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 8 Apr 2010 08:39:31 -0000 Received: (qmail 53639 invoked by uid 500); 8 Apr 2010 08:39:31 -0000 Delivered-To: jmurphy@example.com Received: (qmail 53528 invoked by uid 500); 8 Apr 2010 08:39:29 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 53508 invoked by uid 99); 8 Apr 2010 08:39:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Apr 2010 08:39:28 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jmurphy@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Apr 2010 08:39:23 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <jmurphy@example.com>) id 1NznGM-0005FR-Tr for jmurphy@example.com; Thu, 08 Apr 2010 01:38:58 -0700 Message-ID: <jmurphy@example.com> Date: Thu, 8 Apr 2010 01:38:58 -0700 (PDT) From: Michael Sparer <jmurphy@example.com> To: jmurphy@example.com Subject: Re: Wicket Stuff projects with failing SVN configurations In-Reply-To: <jmurphy@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jmurphy@example.com References: <jmurphy@example.com> I just had a look at wicket stuff rome and saw that the current build is broken. It seems like wicketstuff-rome got moved to the 1.3 branch, but its SVN configuration still points to the trunk. I've already upgraded wicketstuff-rome to wicket 1.4 and rome 1.0 (not that much work with only two classes involved ;-)) and commited it into the wicketstuff trunk. Please grant me the (teamcity-)rights to manage both wicketstuff-rome in the 1.3 branch and the new one in trunk - my username both on sf, teamcity and jira is msparer cheers, Michael Martijn Dashorst wrote: > > All, > > A couple projects have failing SVN configurations and return 404 from > the sf.net repo. > > Can the maintainers for these projects please take a look? > > It involves: > > * Wicket Stuff JavaEE > * Wicket Stuff Rome > * Wicket-Security 1.4.x > * wicketstuff-jmx-panel > > Thanks! > > Martijn > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.4 increases type safety for web applications > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4 > > ----- Michael Sparer http://techblog.molindo.at -- View this message in context: http://old.nabble.com/Wicket-Stuff-projects-with-failing-SVN-configurations-tp26803260p28175744.html Sent from the Wicket - Dev mailing list jmurphy@example.com. From jmurphy@example.com Sun Apr 11 21:08:24 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 34080 invoked from network); 11 Apr 2010 21:08:24 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 11 Apr 2010 21:08:24 -0000 Received: (qmail 21478 invoked by uid 500); 11 Apr 2010 21:08:24 -0000 Delivered-To: jmurphy@example.com Received: (qmail 21433 invoked by uid 500); 11 Apr 2010 21:08:23 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 21425 invoked by uid 99); 11 Apr 2010 21:08:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Apr 2010 21:08:23 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO smtp.rivulet.ca) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Apr 2010 21:08:16 +0000 Received: from [83.161.120.155] (bas3-toronto48-1176441784.dsl.bell.ca [83.161.120.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.rivulet.ca (Postfix) with ESMTPSA id E48CD641FB for <jmurphy@example.com>; Sun, 11 Apr 2010 17:07:50 -0400 (EDT) Message-ID: <jmurphy@example.com> Date: Sun, 11 Apr 2010 17:07:46 -0400 From: Michael O'Cleirigh <jmurphy@example.com> User-Agent: Thunderbird 83.161.120.155 (Windows/20100228) MIME-Version: 1.0 To: jmurphy@example.com Subject: How does TeamCity collect Wicketsuff SVN changes (post commit hook or polling)? References: <jmurphy@example.com> <jmurphy@example.com> <jmurphy@example.com> In-Reply-To: <jmurphy@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello, This message is a follow up to the TeamCity access issue with jmurphy@example.com. I asked about the access problem in the source forge irc support but the response was to have a project admin open up a ticket which is what didn't work last time. I was wondering if TeamCity was setup to continuously poll the SVN repository or if a post commit hook was being used? I would think that triggering svn update only after a developer commits would generate less requests and hopefully prevent the build server from being blacklisted. At work we use the post commit hook to fire a wget into our Hudson CI server that in turn triggers the svn update and build. TeamCity seems to support the same: http://confluence.jetbrains.net/display/TCD5/Accessing+Server+by+HTTP#AccessingServerbyHTTP-TriggeringaBuildFromScript Sourceforge won't let projects directly edit the svn/hooks/post-commit file. Instead they support several scripts that can be configured by a project admin. There is no wget option available; the closest is the 'svnnotify' script that can send an email when a commit occurs. I can provide a dedicated email address for this purpose and offer to write a script to convert the commit notifications into wget calls into teamcity which would active the build. Regards, Mike > Correct as always. > > I think Sf were convinced that it was not their problem or something. > We actually switched from Bamboo to TeamCity for that reason.. I also > created a separate project on google called wicketstuff, but we never > could agree on using that instead of sf. > > regards Nino > > 2010/4/1 Igor Vaynberg <jmurphy@example.com>: > >> sf.net keeps banning our TC instance because they think it access svn >> too often. nothing we can do about it. i think nino filed a ticket >> with them that never got resolved. >> >> -igor >> >> On Thu, Apr 1, 2010 at 6:48 AM, Michael O'Cleirigh >> <jmurphy@example.com> wrote: >> >>> Hello, >>> >>> Recently there has been some initiative in organizing more WicketStuff core >>> releases and changes have been going into the sourceforge subversion >>> repository for that effect. >>> >>> But there is a problem with Teamcity not being able to access the >>> wicketstuff repository which prevents the updated artifacts being built and >>> distributed into the maven snapshot repository. I like to only checkout the >>> specific submodules I work on and have m2eclipse resolve the parent from the >>> snapshot repository; but that approach doesn't work when the snapshots are >>> not being created. >>> >>> I searched the dev list archive and there was a problem like this in the >>> past (Re: TeamCity on wicketstuff.org from November 29 2008). >>> >>> Here is a link to the build log with the >>> '//org.tmatesoft.svn.core.SVNException: svn: connection refused by the >>> server'// error: >>> http://wicketstuff.org/teamcity/viewLog.html?buildId=5903&tab=buildResultsDiv&buildTypeId=bt35 >>> >>> It feels like the build server might be blacklisted in some way by >>> sourceforge; although it could be something else. >>> >>> Does anyone know what was done before or have a contact from that time which >>> could be used to get teamcity talking subversion again? >>> >>> Thanks, >>> >>> Mike >>> >>> >>> >>> >>> >>> >> From jmurphy@example.com Mon Apr 12 07:44:27 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 49242 invoked from network); 12 Apr 2010 07:44:27 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 12 Apr 2010 07:44:27 -0000 Received: (qmail 55947 invoked by uid 500); 12 Apr 2010 07:44:26 -0000 Delivered-To: jmurphy@example.com Received: (qmail 55774 invoked by uid 500); 12 Apr 2010 07:44:24 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 55765 invoked by uid 99); 12 Apr 2010 07:44:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Apr 2010 07:44:24 +0000 X-ASF-Spam-Status: No, hits=-1.1 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jmurphy@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-bw0-f220.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Apr 2010 07:44:18 +0000 Received: by bwz20 with SMTP id 20so6119114bwz.32 for <jmurphy@example.com>; Mon, 12 Apr 2010 00:43:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type :content-transfer-encoding; bh=FB8zSL24GAQ0J679eRsy864yyOnruyX76QI4fGM3AJA=; b=Kv1f1cuYpk9SHGcdgaEqeCgkxm0ZIQOpTLlxYZqKOSU3mLEKZK/JY52W0Il7qecvnc N5fHFzmxFZp1ffhFKnqnnkFD/1+bN98+U2PLHmVvQD68Fxuc6o3mxuL/Xce7rvRaegsc 4JSwSXkqSyfP6K0wcFNlT+U1doOfVBCZ5A03g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=Vm2yG2umNthrUc6nI73sSfoFExnJ+X6CH1VnzS2moEdR/zeA8704H62kxOw+PGiR4r PRjlTINyd+d7+81nJ6TndAghQ89NwYuEgAx4gWqDsLhECJPuRwrZWvbWdYMmIq8o5KW/ dQJMDXRaBpiAtC/0x4rDo3yIF0GubOovG/4RY= MIME-Version: 1.0 Received: by 83.161.120.155 with HTTP; Mon, 12 Apr 2010 00:43:36 -0700 (PDT) In-Reply-To: <jmurphy@example.com> References: <jmurphy@example.com> From: Martijn Dashorst <jmurphy@example.com> Date: Mon, 12 Apr 2010 09:43:36 +0200 Received: by 83.161.120.155 with SMTP id p36mr1647149mul.102.1271058236824; Mon, 12 Apr 2010 00:43:56 -0700 (PDT) Message-ID: <jmurphy@example.com> Subject: Fwd: [NOTICE] compromised jira passwords To: jmurphy@example.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable ---------- Forwarded message ---------- From: Joe Schaefer <jmurphy@example.com> Date: Sat, Apr 10, 2010 at 7:24 PM Subject: [NOTICE] compromised jira passwords To: jmurphy@example.com Hello Apache community@ [1], As you are probably aware we have been working to restore services that have been compromised by a very targetted attack against Apache's jira installation. =A0The good news is that jira is back online, with bugzilla and confluence soon to follow [2]. =A0The bad news is that the hacker was able to rejigger jira's code to sniff any cookies and passwords sent to the server between April 6 and April 9. =A0If you used jira at all this week, including via IDE's that interface via SOAP, it is IMPERATIVE that you take time to immediately reset your jira password, and possibly your ldap password if those match up. If you have admin privs in jira your password was reset by us, so you'll need to use the password reset form in jira to regain access. To have a reset password mailed to your contact information in jira, visit https://issues.apache.org/jira/secure/ForgotPassword!default.jspa When you do login to jira be sure to double-check your contact info. To change your ldap password login to people.apache.org and run /usr/sbin/passwd, or else visit https://svn.apache.org/change-password . Thanks for your patience and diligence in this matter. =A0A blog post will be forthcoming which will provide details of the attack and what we have done to mitigate future hack attempts. [1] feel free to forward this note to any other apache mailing list, public or private. [2] at this time we do not believe the hacker compromised the confluence and bugzilla installs, but we are awaiting confirmation from our admins before bringing those back online. --------------------------------------------------------------------- To unsubscribe, e-mail: jmurphy@example.com For additional commands, e-mail: jmurphy@example.com --=20 Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4 From jmurphy@example.com Fri Apr 16 06:27:57 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 18062 invoked from network); 16 Apr 2010 06:27:57 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 16 Apr 2010 06:27:57 -0000 Received: (qmail 5625 invoked by uid 500); 16 Apr 2010 06:27:57 -0000 Delivered-To: jmurphy@example.com Received: (qmail 5405 invoked by uid 500); 16 Apr 2010 06:27:55 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 5397 invoked by uid 99); 16 Apr 2010 06:27:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 06:27:54 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO mail-yw0-f191.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 06:27:47 +0000 Received: by ywh29 with SMTP id 29so2204429ywh.14 for <jmurphy@example.com>; Thu, 15 Apr 2010 23:27:26 -0700 (PDT) MIME-Version: 1.0 Received: by 83.161.120.155 with HTTP; Thu, 15 Apr 2010 23:27:24 -0700 (PDT) Date: Fri, 16 Apr 2010 01:27:24 -0500 Received: by 83.161.120.155 with SMTP id u19mr1340860ybm.243.1271399244169; Thu, 15 Apr 2010 23:27:24 -0700 (PDT) Message-ID: <jmurphy@example.com> Subject: Handling errors on a per-component basis? From: Jeremy Thomerson <jmurphy@example.com> To: Wicket Development <jmurphy@example.com> Content-Type: multipart/alternative; boundary=001e680f16305146bf048454b479 X-Virus-Checked: Checked by ClamAV on apache.org --001e680f16305146bf048454b479 Content-Type: text/plain; charset=ISO-8859-1 Core devs (and others), I had someone ask me how to handle errors on a per-component basis. That is, if a component on the page encounters an error during rendering, it would be nice to be able to just replace it with an empty panel that says "foo component encountered an error". Obviously, there are only certain places you would want this, but it could be valuable for certain situations. So, I have a couple ideas on how to implement it. None of them seem very clean. I'd like your feedback. Basically, I need to be able to wrap Component#renderComponent(final MarkupStream markupStream) so that I can catch any error coming out of there. So, the flow should be something like: 1. somehow cache exactly where the response is (before the component writes something to it) - either by copying the internal buffers, etc, or whatever, but not letting it go back to the client until the component is done being rendered 2. then, inside of a try / catch, I could call super.renderComponent(final MarkupStream markupStream) so that the component is rendered (calling Response#write to output it's stuff....) 3. then, if I caught an error, I rollback the response buffer to where it was before that component, and write my "this component didn't work" thing, and then close the tag and continue rendering Because most of the methods that actually do the rendering are final, and this is hard to accomplish. And, of course, I can't actually globally override a method in Component. Behaviors get calls before and after render, as well as on an error, but they can't stop the error from being rethrown. So, it appears that the only way to do the above is by creating a proxy class that wraps that single renderComponent method in Component. This dynamic proxy could be created in a component instantiation listener. Then I could proxy for that method. Do you have any other options or thoughts? -- Jeremy Thomerson http://www.wickettraining.com --001e680f16305146bf048454b479-- From jmurphy@example.com Fri Apr 16 06:42:53 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 20133 invoked from network); 16 Apr 2010 06:42:53 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 16 Apr 2010 06:42:53 -0000 Received: (qmail 16328 invoked by uid 500); 16 Apr 2010 06:42:52 -0000 Delivered-To: jmurphy@example.com Received: (qmail 15950 invoked by uid 500); 16 Apr 2010 06:42:50 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 15942 invoked by uid 99); 16 Apr 2010 06:42:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 06:42:49 +0000 X-ASF-Spam-Status: No, hits=-1.1 required=10.0 tests=AWL,FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jmurphy@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-gy0-f173.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 06:42:44 +0000 Received: by gyd5 with SMTP id 5so1033451gyd.32 for <jmurphy@example.com>; Thu, 15 Apr 2010 23:42:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type :content-transfer-encoding; bh=PnSyiXVO7OiE03wmYUTMufwf9ETCY6m6HjbZm/LbO54=; b=FB0GQzKQMpewIeFpIkHNHqerwrR2MWrWJrwvz49kbPAq3tTDGIcQQltEDm9Z8EjwL6 0zsbAs9hZQbF42etB/6xuzf9uRturpQqK7J87stp0H79MuuGldN5aipdv0Ocz/ROdBFV +8hB36IBvEbTLOs4xlQgdyWiXn8k9b5DUsUUc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=PaU+6r1aHYrn26KO5EZVRrNiTPHyMj2iP38RoR8yUw+NK+MLKcmdEKiU7H0+X2MN+o RvbUPKlJSemksAlAKQ1L4KTKyNS27k7jvHVE+vHysK6C9thcjJI33zgzBrQyP5DH+2qG tYatedPurssFr9fpGfBKqv9e9g1HVC3E/xi9I= MIME-Version: 1.0 Received: by 83.161.120.155 with HTTP; Thu, 15 Apr 2010 23:42:00 -0700 (PDT) In-Reply-To: <jmurphy@example.com> References: <jmurphy@example.com> From: Igor Vaynberg <jmurphy@example.com> Date: Thu, 15 Apr 2010 23:42:00 -0700 Received: by 83.161.120.155 with SMTP id h13mr2388199ann.47.1271400140194; Thu, 15 Apr 2010 23:42:20 -0700 (PDT) Message-ID: <jmurphy@example.com> Subject: Re: Handling errors on a per-component basis? To: jmurphy@example.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable what if a component throws an exception during onbeforerender? what if it throws an exception during a post-order traversal? there are a lot of dependencies, im not sure how feasible this idea is. whats the usecase? the only one that makes sense is if an error is thrown during model.getobject() and we want to handle it then? why not make the model exception-aware then? or hook in directly there and skip the component render? as far as "remembering" where the response is i think you can accomplish it by swapping a different response in. like the transformer behaviors do - which actually come pretty close to what you want... -igor On Thu, Apr 15, 2010 at 11:27 PM, Jeremy Thomerson <jmurphy@example.com> wrote: > Core devs (and others), > > =A0I had someone ask me how to handle errors on a per-component basis. = =A0That > is, if a component on the page encounters an error during rendering, it > would be nice to be able to just replace it with an empty panel that says > "foo component encountered an error". =A0Obviously, there are only certai= n > places you would want this, but it could be valuable for certain situatio= ns. > > =A0So, I have a couple ideas on how to implement it. =A0None of them seem= very > clean. =A0I'd like your feedback. =A0Basically, I need to be able to > wrap Component#renderComponent(final MarkupStream markupStream) so that I > can catch any error coming out of there. =A0So, the flow should be someth= ing > like: > > =A0 1. somehow cache exactly where the response is (before the component > =A0 writes something to it) - either by copying the internal buffers, etc= , or > =A0 whatever, but not letting it go back to the client until the componen= t is > =A0 done being rendered > =A0 2. then, inside of a try / catch, I could call > =A0 super.renderComponent(final MarkupStream markupStream) so that the co= mponent > =A0 is rendered (calling Response#write to output it's stuff....) > =A0 3. then, if I caught an error, I rollback the response buffer to wher= e it > =A0 was before that component, and write my "this component didn't work" = thing, > =A0 and then close the tag and continue rendering > > Because most of the methods that actually do the rendering are final, and > this is hard to accomplish. =A0And, of course, I can't actually globally > override a method in Component. Behaviors get calls before and after rend= er, > as well as on an error, but they can't stop the error from being rethrown= . > > So, it appears that the only way to do the above is by creating a proxy > class that wraps that single renderComponent method in Component. =A0This > dynamic proxy could be created in a component instantiation listener. =A0= Then > I could proxy for that method. =A0Do you have any other options or though= ts? > > -- > Jeremy Thomerson > http://www.wickettraining.com > From jmurphy@example.com Fri Apr 16 12:28:18 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 21967 invoked from network); 16 Apr 2010 12:28:18 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 16 Apr 2010 12:28:18 -0000 Received: (qmail 86795 invoked by uid 500); 16 Apr 2010 12:28:17 -0000 Delivered-To: jmurphy@example.com Received: (qmail 86703 invoked by uid 500); 16 Apr 2010 12:28:17 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 86694 invoked by uid 99); 16 Apr 2010 12:28:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 12:28:16 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO qw-out-1920.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 12:28:08 +0000 Received: by qw-out-1920.google.com with SMTP id 5so916986qwf.2 for <jmurphy@example.com>; Fri, 16 Apr 2010 05:27:47 -0700 (PDT) Received: by 83.161.120.155 with SMTP id ld12mr2079324qcb.92.1271420867309; Fri, 16 Apr 2010 05:27:47 -0700 (PDT) Received: from Inbox ([83.161.120.155]) by mx.google.com with ESMTPS id v26sm2397798qce.13.283.161.120.155.27.42 (version=SSLv3 cipher=RC4-MD5); Fri, 16 Apr 2010 05:27:46 -0700 (PDT) Message-ID: <jmurphy@example.com> MIME-Version: 1.0 content-class: From: Jeremy Thomerson <jmurphy@example.com> Subject: RE: Handling errors on a per-component basis? Date: Fri, 16 Apr 2010 07:27:55 -0500 Importance: normal X-Priority: 3 To: <jmurphy@example.com> Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-Virus-Checked: Checked by ClamAV on apache.org Use case is that you may occasionally have some component on the page (say = a graph or a chart) that isn't extremely critical to the function of the pa= ge. Maybe it has to get data from a third party, and occasionally that wil= l fail. And rather than aborting the whole page, you'd rather it be replac= ed with an empty placeholder. Of course for the third-party data example, you could add error handling to= the model. But you end up with this boilerplate all over your code potenti= ally. So, it'd be nice to have a more global way of responding to an error= for a single component and moving on, perhaps marking components that coul= d "fail gracefully" with some sort of interface or annotation. Jeremy Thomerson http://www.wickettraining.com -- sent from a wireless device -----Original Message----- From: Igor Vaynberg <jmurphy@example.com> Sent: Friday, April 16, 2010 1:42 AM To: jmurphy@example.com Subject: Re: Handling errors on a per-component basis? what if a component throws an exception during onbeforerender? what if it throws an exception during a post-order traversal? there are a lot of dependencies, im not sure how feasible this idea is. whats the usecase? the only one that makes sense is if an error is thrown during model.getobject() and we want to handle it then? why not make the model exception-aware then? or hook in directly there and skip the component render? as far as "remembering" where the response is i think you can accomplish it by swapping a different response in. like the transformer behaviors do - which actually come pretty close to what you want... -igor On Thu, Apr 15, 2010 at 11:27 PM, Jeremy Thomerson <jmurphy@example.com> wrote: > Core devs (and others), > > =A0I had someone ask me how to handle errors on a per-component basis. = =A0That > is, if a component on the page encounters an error during rendering, it > would be nice to be able to just replace it with an empty panel that says > "foo component encountered an error". =A0Obviously, there are only certai= n > places you would want this, but it could be valuable for certain situatio= ns. > > =A0So, I have a couple ideas on how to implement it. =A0None of them seem= very > clean. =A0I'd like your feedback. =A0Basically, I need to be able to > wrap Component#renderComponent(final MarkupStream markupStream) so that I > can catch any error coming out of there. =A0So, the flow should be someth= ing > like: > > =A0 1. somehow cache exactly where the response is (before the component > =A0 writes something to it) - either by copying the internal buffers, etc= , or > =A0 whatever, but not letting it go back to the client until the componen= t is > =A0 done being rendered > =A0 2. then, inside of a try / catch, I could call > =A0 super.renderComponent(final MarkupStream markupStream) so that the co= mponent > =A0 is rendered (calling Response#write to output it's stuff....) > =A0 3. then, if I caught an error, I rollback the response buffer to wher= e it > =A0 was before that component, and write my "this component didn't work" = thing, > =A0 and then close the tag and continue rendering > > Because most of the methods that actually do the rendering are final, and > this is hard to accomplish. =A0And, of course, I can't actually globally > override a method in Component. Behaviors get calls before and after rend= er, > as well as on an error, but they can't stop the error from being rethrown= From jmurphy@example.com Fri Apr 16 15:25:36 2010 Return-Path: <jmurphy@example.com> Delivered-To: jmurphy@example.com Received: (qmail 93306 invoked from network); 16 Apr 2010 15:25:36 -0000 Received: from unknown (HELO mail.apache.org) (83.161.120.155) by 83.161.120.155 with SMTP; 16 Apr 2010 15:25:36 -0000 Received: (qmail 98192 invoked by uid 500); 16 Apr 2010 15:25:36 -0000 Delivered-To: jmurphy@example.com Received: (qmail 98166 invoked by uid 500); 16 Apr 2010 15:25:35 -0000 Mailing-List: contact jmurphy@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:jmurphy@example.com> List-Unsubscribe: <mailto:jmurphy@example.com> List-Post: <mailto:jmurphy@example.com> List-Id: <dev.wicket.apache.org> Reply-To: jmurphy@example.com Delivered-To: mailing list jmurphy@example.com Received: (qmail 98158 invoked by uid 99); 16 Apr 2010 15:25:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 15:25:35 +0000 X-ASF-Spam-Status: No, hits=-1.1 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jmurphy@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-gx0-f213.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 15:25:30 +0000 Received: by gxk5 with SMTP id 5so1499200gxk.6 for <jmurphy@example.com>; Fri, 16 Apr 2010 08:25:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type :content-transfer-encoding; bh=BR+Q0/0waQa9o9BLNVKzF0Y2smJtabuYcL6nlCndZhk=; b=MstBx0qwNPYTQh4dwkPWzquRlkGeLQ1nkoZ8g3ZuZSfsO6N+uCjbLsIqZX1vYr47sW pC5gnffLjIl+Kel/2i11dq5iHaYU+uSck0QEP5NHSaT6P1oqclPEs8411qtQ4Zp2xKck kc5lFq2QTcevk7Xps0N9OR+Fi4ng4Qi/C8rAM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=Jcd/FzA3/I+vx6jPHm/IuDU9pvS7dZ3/wkjF/KPKkPTSpybbiF1rAQj+9qOvDCoHg/ 1cdbMh0yFomeHAcFqfPh7pbcowH8Abwdxxw8fByftKEPrVfAZpIRH/nzCViTbISncvoF Tkz4Ms6viKBOuGm2kdrP37sJnzWNBX/VO8m+Y= MIME-Version: 1.0 Received: by 83.161.120.155 with HTTP; Fri, 16 Apr 2010 08:24:49 -0700 (PDT) In-Reply-To: <jmurphy@example.com> References: <jmurphy@example.com> From: Igor Vaynberg <jmurphy@example.com> Date: Fri, 16 Apr 2010 08:24:49 -0700 Received: by 83.161.120.155 with SMTP id f7mr3878683ann.232.1271431509193; Fri, 16 Apr 2010 08:25:09 -0700 (PDT) Message-ID: <jmurphy@example.com> Subject: Re: Handling errors on a per-component basis? To: jmurphy@example.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable why not use an ajax lazy load panel for this, perhaps one that fails gracef= ully? -igor On Fri, Apr 16, 2010 at 5:27 AM, Jeremy Thomerson <jmurphy@example.com> wrote: > Use case is that you may occasionally have some component on the page (sa= y a graph or a chart) that isn't extremely critical to the function of the = page. =A0Maybe it has to get data from a third party, and occasionally that= will fail. =A0And rather than aborting the whole page, you'd rather it be = replaced with an empty placeholder. > > Of course for the third-party data example, you could add error handling = to the model. But you end up with this boilerplate all over your code poten= tially. =A0So, it'd be nice to have a more global way of responding to an e= rror for a single component and moving on, perhaps marking components that = could "fail gracefully" with some sort of interface or annotation. > > > Jeremy Thomerson > http://www.wickettraining.com > -- sent from a wireless device > > > -----Original Message----- > From: Igor Vaynberg <jmurphy@example.com> > Sent: Friday, April 16, 2010 1:42 AM > To: jmurphy@example.com > Subject: Re: Handling errors on a per-component basis? > > what if a component throws an exception during onbeforerender? > > what if it throws an exception during a post-order traversal? > > there are a lot of dependencies, im not sure how feasible this idea > is. whats the usecase? the only one that makes sense is if an error is > thrown during model.getobject() and we want to handle it then? why not > make the model exception-aware then? or hook in directly there and > skip the component render? > > as far as "remembering" where the response is i think you can > accomplish it by swapping a different response in. like the > transformer behaviors do - which actually come pretty close to what > you want... > > -igor > > On Thu, Apr 15, 2010 at 11:27 PM, Jeremy Thomerson > <jmurphy@example.com> wrote: >> Core devs (and others), >> >> =A0I had someone ask me how to handle errors on a per-component basis. = =A0That >> is, if a component on the page encounters an error during rendering, it >> would be nice to be able to just replace it with an empty panel that say= s >> "foo component encountered an error". =A0Obviously, there are only certa= in >> places you would want this, but it could be valuable for certain situati= ons. >> >> =A0So, I have a couple ideas on how to implement it. =A0None of them see=
{'source': 'Apache Software Foundation Public Mail Archives'}