From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 08:16:21 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 38830 invoked from network); 1 Feb 2006 08:16:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 08:16:21 -0000 Received: (qmail 55660 invoked by uid 500); 1 Feb 2006 08:16:19 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 55646 invoked by uid 500); 1 Feb 2006 08:16:18 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 55635 invoked by uid 99); 1 Feb 2006 08:16:18 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 00:16:18 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [83.161.120.155] (HELO mx2.datanet.hu) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 00:16:17 -0800 Received: from norbi (nilus-30.adsl.datanet.hu [83.161.120.155]) by mx2.datanet.hu (DataNet) with SMTP id 0B7F21241E7 for <johnsonbrian@example.com>; Wed, 1 Feb 2006 09:15:53 +0100 (CET) Message-ID: <254a01c62707$baec23d0$0101a8c0@norbi> From: =?iso-8859-1?Q?Norbert_S=E1ndor?= <johnsonbrian@example.com> To: "Tapestry development" <johnsonbrian@example.com> References: <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts Date: Wed, 1 Feb 2006 09:15:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > I agree that <service> was easier than the HM approach, which is > (infinitely) flexible. I think that the most perfect solution is if Hivemind supports annotations therefore engine service implementations can define their dependencies using annotations. (+ autowiring) > 1) Keep backwards compatibility and evolve the code base (give or take) > 2) Sacrifice backwards compatibility, but create the simpler, less > ambiguous (easier to learn) framework people want 2) > My current vision is that the 4.1 code base will be about creating new > components, including Ajax integration. Most of the innovation is Will 4.1 based on DOJO? (= Tacos and Tapestry 4 will be merged?) I think it is very important to fully support DOJO (now both Tapestry and DOJO are stable): - some unified (documented) way to convert DOJO components to Tapestry components - make them working in case of "partial" refresh - etc (more active dojo/tacos users may continue the list) > - Annotations based. JDK 1.5. Great, I would love generics in the API methods as well. (Currently my code is full of warnings because of lack of java5 support.) > - No XML for pages and components. Just HTML and Annotations. I don't like this, separating layout and component defs is a very good thing in tapestry! I define components only in the .jwc/.page file, even in case of the most simple RenderBody. And I think @Component is not a clean solution especially when the component has many subcomponents, the class file becomes "ugly". > ... others Great! Regards, Norbi --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 11:22:41 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 35839 invoked from network); 1 Feb 2006 11:22:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 11:22:40 -0000 Received: (qmail 75898 invoked by uid 500); 1 Feb 2006 11:22:39 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 75718 invoked by uid 500); 1 Feb 2006 11:22:38 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 75707 invoked by uid 99); 1 Feb 2006 11:22:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 03:22:38 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of johnsonbrian@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ciao.gmane.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 03:22:37 -0800 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1F4G3Y-0000Xw-2Q for johnsonbrian@example.com; Wed, 01 Feb 2006 12:21:48 +0100 Received: from d176234.adsl.hansenet.de ([83.161.120.155]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <johnsonbrian@example.com>; Wed, 01 Feb 2006 12:21:48 +0100 Received: from rpiterman by d176234.adsl.hansenet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <johnsonbrian@example.com>; Wed, 01 Feb 2006 12:21:48 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: johnsonbrian@example.com From: Ron Piterman <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts Date: Wed, 01 Feb 2006 12:22:43 +0100 Lines: 69 Message-ID: <johnsonbrian@example.com> References: <johnsonbrian@example.com> <254a01c62707$baec23d0$0101a8c0@norbi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: johnsonbrian@example.com X-Gmane-NNTP-Posting-Host: d176234.adsl.hansenet.de User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) X-Accept-Language: en-us, en In-Reply-To: <254a01c62707$baec23d0$0101a8c0@norbi> Sender: news <johnsonbrian@example.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N While dojo seems a very good library, there are some serious considerations about making tapestry really dependeant on it - I would like to know if that is going to be the case for 4.1... Well, as unpopular as it may sound, I find that very unacceptable - dojo, as hip as it is, has also many disadvantages - like getting really hard on the browser for very basic tasks - so page load time is very long, getting high latency also when using top hardware - I don't want to know what happens when and if using old browsers and hardware - I think if tapestry is heading the way of being a web framework for ajax applications, not giving the basic sleek functionality for good old web 1.0 - well - this requires some discussion from the community. currently, all JS is clean and functions well, I hope it stays that way, *enabling* one to use JS libraries such as Dojo, but not *imposing* one to use a certain one... Cheers, Ron Norbert Sándor wrote: >> I agree that <service> was easier than the HM approach, which is >> (infinitely) flexible. > > I think that the most perfect solution is if Hivemind supports > annotations therefore engine service implementations can define their > dependencies using annotations. (+ autowiring) > >> 1) Keep backwards compatibility and evolve the code base (give or take) >> 2) Sacrifice backwards compatibility, but create the simpler, less >> ambiguous (easier to learn) framework people want > > 2) > >> My current vision is that the 4.1 code base will be about creating new >> components, including Ajax integration. Most of the innovation is > > Will 4.1 based on DOJO? (= Tacos and Tapestry 4 will be merged?) > I think it is very important to fully support DOJO (now both Tapestry > and DOJO are stable): > - some unified (documented) way to convert DOJO components to Tapestry > components > - make them working in case of "partial" refresh > - etc (more active dojo/tacos users may continue the list) > >> - Annotations based. JDK 1.5. > > Great, I would love generics in the API methods as well. (Currently my > code is full of warnings because of lack of java5 support.) > >> - No XML for pages and components. Just HTML and Annotations. > > I don't like this, separating layout and component defs is a very good > thing in tapestry! > I define components only in the .jwc/.page file, even in case of the > most simple RenderBody. And I think @Component is not a clean solution > especially when the component has many subcomponents, the class file > becomes "ugly". > >> ... others > > Great! > > Regards, > Norbi --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 11:41:53 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 44705 invoked from network); 1 Feb 2006 11:41:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 11:41:40 -0000 Received: (qmail 3377 invoked by uid 500); 1 Feb 2006 11:41:32 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 3363 invoked by uid 500); 1 Feb 2006 11:41:32 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 3352 invoked by uid 99); 1 Feb 2006 11:41:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 03:41:31 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of johnsonbrian@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail.canfactory.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 01 Feb 2006 03:41:30 -0800 Received: from webmail.canfactory.com ([83.161.120.155]) by mail.canfactory.com (SMSSMTP 83.161.120.155) with SMTP id M2006020111410902273 for <johnsonbrian@example.com>; Wed, 01 Feb 2006 11:41:09 GMT Content-class: urn:content-classes:message Subject: RE: Re: Tapestry 5 thoughts MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 1 Feb 2006 11:41:23 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Message-ID: <johnsonbrian@example.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Tapestry 5 thoughts thread-index: AcYnIdFRXSxCPUtASQmsjhZuMPScrQAAmhpg From: "Joe Trewin" <johnsonbrian@example.com> To: "Tapestry development" <johnsonbrian@example.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I agree with Ron. Personally I use some homegrown Javascript libraries = to do just what I need (and no more), so wouldn't want to be forced to = use external heavy-duty libraries. Nothing wrong with including it if desired, as long as it can be turned = off or replaced in someway (something that may obviously impact on Tacos = components). -----Original Message----- From: news [mailto:johnsonbrian@example.com] On Behalf Of Ron Piterman Sent: 01 February 2006 11:23 To: johnsonbrian@example.com Subject: Re: Tapestry 5 thoughts While dojo seems a very good library, there are some serious = considerations about making tapestry really dependeant on it - I would like to know if that is going to be the case for 4.1... Well, as unpopular as it may sound, I find that very unacceptable - = dojo, as hip as it is, has also many disadvantages - like getting really = hard on the browser for very basic tasks - so page load time is very = long, getting high latency also when using top hardware - I don't want = to know what happens when and if using old browsers and hardware - I think if tapestry is heading the way of being a web framework for ajax = applications, not giving the basic sleek functionality for good old web = 1.0 - well - this requires some discussion from the community. currently, all JS is clean and functions well, I hope it stays that way, *enabling* one to use JS libraries such as Dojo, but not *imposing* one = to use a certain one... Cheers, Ron Norbert S=E1ndor wrote: >> I agree that <service> was easier than the HM approach, which is >> (infinitely) flexible. >=20 > I think that the most perfect solution is if Hivemind supports=20 > annotations therefore engine service implementations can define their=20 > dependencies using annotations. (+ autowiring) >=20 >> 1) Keep backwards compatibility and evolve the code base (give or=20 >> take) >> 2) Sacrifice backwards compatibility, but create the simpler, less=20 >> ambiguous (easier to learn) framework people want >=20 > 2) >=20 >> My current vision is that the 4.1 code base will be about creating=20 >> new components, including Ajax integration. Most of the innovation is >=20 > Will 4.1 based on DOJO? (=3D Tacos and Tapestry 4 will be merged?) I=20 > think it is very important to fully support DOJO (now both Tapestry=20 > and DOJO are stable): > - some unified (documented) way to convert DOJO components to Tapestry = > components > - make them working in case of "partial" refresh > - etc (more active dojo/tacos users may continue the list) >=20 >> - Annotations based. JDK 1.5. >=20 > Great, I would love generics in the API methods as well. (Currently my = > code is full of warnings because of lack of java5 support.) >=20 >> - No XML for pages and components. Just HTML and Annotations. >=20 > I don't like this, separating layout and component defs is a very good = > thing in tapestry! > I define components only in the .jwc/.page file, even in case of the=20 > most simple RenderBody. And I think @Component is not a clean solution = > especially when the component has many subcomponents, the class file=20 > becomes "ugly". >=20 >> ... others >=20 > Great! >=20 > Regards, > Norbi --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 12:26:34 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 71555 invoked from network); 1 Feb 2006 12:26:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 12:26:34 -0000 Received: (qmail 83597 invoked by uid 500); 1 Feb 2006 12:26:32 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 83582 invoked by uid 500); 1 Feb 2006 12:26:32 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 83571 invoked by uid 99); 1 Feb 2006 12:26:31 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO vmgump.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 04:26:31 -0800 Date: Wed, 01 Feb 2006 04:22:10 PST From: Howard M. Lewis Ship <johnsonbrian@example.com> To: johnsonbrian@example.com Subject: [GUMP@vmgump]: Project jakarta-tapestry (in module jakarta-tapestry) failed X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at johnsonbrian@example.com. Project jakarta-tapestry has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 18 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-tapestry : Component-based web application framework organized around i... Full details are available at: http://vmgump.apache.org/gump/public/jakarta-tapestry/jakarta-tapestry/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [tapestry-01022006.jar] identifier set to project name -DEBUG- Dependency on jakarta-hivemind exists, no need to add for property hivebuild.dir. -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-tapestry/jakarta-tapestry/gump_work/build_jakarta-tapestry_jakarta-tapestry.html Work Name: build_jakarta-tapestry_jakarta-tapestry (Type: Build) Work ended in a state of : Failed Elapsed: 10 secs Command Line: java -Djava.awt.headless=true -DBASEDIR=/usr/local/gump/public/workspace/jakarta-tapestry/framework -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djava.classes.dir=target/classes -Djunit-available=true -Ddownload-warning-marker-displayed=true -Dframework.version=01022006 -Dtest.classes.dir=target/test-classes -Dhivebuild.dir=/usr/local/gump/public/workspace/jakarta-hivemind/hivebuild -Ddownload-alert-shown=true [Working Directory: /usr/local/gump/public/workspace/jakarta-tapestry] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-hivemind/hivebuild/target/classes:/usr/local/gump/public/workspace/jakarta-tapestry/framework/target/classes:/usr/local/gump/public/workspace/jakarta-tapestry/contrib/classes:/usr/local/gump/public/workspace/jakarta-tapestry/examples/VlibBeans/classes:/usr/local/gump/public/workspace/jakarta-tapestry/examples/Workbench/target/classes:/usr/local/gump/public/workspace/jakarta-tapestry/framework/target/test-classes:/usr/local/gump/public/workspace/jakarta-tapestry/framework/src/descriptor:/usr/local/gump/public/workspace/jakarta-tapestry/framework/src/test:/usr/local/gump/public/workspace/jakarta-tapestry/framework/src/test-data:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/packages/asm-1.5.2/lib/asm-analysis-1.5.2.jar:/usr/local/gump/packages/asm-1.5.2/lib/asm-xml-1.5.2.jar:/usr/local/gump/packages/asm-1.5.2/lib/asm-attrs-1.5.2.jar:/usr/local/gump/packages/asm-1.5.2/lib/asm-1.5.2.jar:/usr/local/gump/packages/asm-1.5.2/lib/kasm-1.5.2.jar:/usr/local/gump/packages/asm-1.5.2/lib/asm-tree-1.5.2.jar:/usr/local/gump/packages/asm-1.5.2/lib/asm-util-1.5.2.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/codec/dist/commons-codec-01022006.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/usr/local/gump/public/workspace/jakarta-commons/fileupload/target/commons-fileupload-01022006.jar:/usr/local/gump/public/workspace/jakarta-commons/io/build/jakarta-commons-io-01022006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-01022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-01022006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-01022006.jar:/usr/local/gump/packages/easymock1.2_Java1.3/easymock.jar:/usr/local/gump/packages/easymockclassextension1.2/easymockclassextension.jar:/usr/local/gump/public/workspace/jakarta-hivemind/target/hivemind-01022006.jar:/usr/local/gump/public/workspace/jakarta-hivemind/target/hivemind-lib-01022006.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-01022006.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/javassist/javassist.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-01022006.jar:/usr/local/gump/packages/ognl-2.6.7/ognl-2.6.7.jar:/usr/local/gump/packages/ejb-2_0-fr/ejb.jar:/usr/local/gump/packages/jCharts-0.7.5/jCharts-0.7.5.jar --------------------------------------------- Buildfile: build.xml install: compile-dependencies: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-tapestry/ext-package/lib -display-download-warning: [grabber] Downloading http://www.ibiblio.org/maven/commons-codec/jars/commons-codec-1.3.jar to /x1/gump/public/workspace/jakarta-tapestry/ext-package/lib/commons-codec-1.3.jar [copy] Copying 1 file to /tmp/jakarta-tapestry/tapestry/target/module-lib/compile/commons-codec [copy] Copying /x1/gump/public/workspace/jakarta-tapestry/ext-package/lib/commons-codec-1.3.jar to /tmp/jakarta-tapestry/tapestry/target/module-lib/compile/commons-codec/commons-codec-1.3.jar -display-download-warning: [grabber] Downloading http://www.ibiblio.org/maven/commons-fileupload/jars/commons-fileupload-1.0.jar to /x1/gump/public/workspace/jakarta-tapestry/ext-package/lib/commons-fileupload-1.0.jar [copy] Copying 1 file to /tmp/jakarta-tapestry/tapestry/target/module-lib/compile/commons-fileupload [copy] Copying /x1/gump/public/workspace/jakarta-tapestry/ext-package/lib/commons-fileupload-1.0.jar to /tmp/jakarta-tapestry/tapestry/target/module-lib/compile/commons-fileupload/commons-fileupload-1.0.jar -display-download-warning: [grabber] Downloading http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.4.jar to /x1/gump/public/workspace/jakarta-tapestry/ext-package/lib/commons-logging-1.0.4.jar [copy] Copying 1 file to /tmp/jakarta-tapestry/tapestry/target/module-lib/compile/commons-logging [copy] Copying /x1/gump/public/workspace/jakarta-tapestry/ext-package/lib/commons-logging-1.0.4.jar to /tmp/jakarta-tapestry/tapestry/target/module-lib/compile/commons-logging/commons-logging-1.0.4.jar -display-download-warning: [grabber] Downloading http://www.ibiblio.org/maven/hivemind/jars/hivemind-1.2-alpha-1.jar to /x1/gump/public/workspace/jakarta-tapestry/ext-package/lib/hivemind-1.2-alpha-1.jar BUILD FAILED /usr/local/gump/public/workspace/jakarta-hivemind/hivebuild/project.xml:52: The following error occurred while executing this line: /usr/local/gump/public/workspace/jakarta-hivemind/hivebuild/project.xml:43: The following error occurred while executing this line: /x1/gump/public/workspace/jakarta-tapestry/framework/build.xml:42: The following error occurred while executing this line: /usr/local/gump/public/workspace/jakarta-hivemind/hivebuild/dependency.xml:112: The following error occurred while executing this line: /usr/local/gump/public/workspace/jakarta-hivemind/hivebuild/dependency.xml:37: Unable to open http://www.ibiblio.org/maven/hivemind/jars/hivemind-1.2-alpha-1.jar: null Total time: 9 seconds --------------------------------------------- To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-tapestry/jakarta-tapestry/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-tapestry/jakarta-tapestry/atom.xml ============================== Gump Tracking Only === Produced by Gump version 2.2. Gump Run 21000001022006, vmgump.apache.org:vmgump-public:21000001022006 Gump E-mail Identifier (unique within run) #31. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 14:16:55 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 51992 invoked from network); 1 Feb 2006 14:16:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 14:16:55 -0000 Received: (qmail 48627 invoked by uid 500); 1 Feb 2006 14:16:51 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 48552 invoked by uid 500); 1 Feb 2006 14:16:51 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 48531 invoked by uid 99); 1 Feb 2006 14:16:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 06:16:51 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [83.161.120.155] (HELO ns.dtqsoftware.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 06:16:50 -0800 Received: (qmail 13118 invoked from network); 1 Feb 2006 09:16:28 -0500 Received: from softdnserror (HELO ?83.161.120.155?) (83.161.120.155) by tor149-99-23-135.dedicated.sprintdsl.ca with SMTP; 1 Feb 2006 09:16:28 -0500 Message-ID: <johnsonbrian@example.com> Date: Wed, 01 Feb 2006 08:16:18 -0600 From: Leonardo Quijano Vincenzi <johnsonbrian@example.com> User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Tapestry development <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts References: <johnsonbrian@example.com> <254a01c62707$baec23d0$0101a8c0@norbi> <johnsonbrian@example.com> In-Reply-To: <johnsonbrian@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 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Dojo should be optional, IMO, but with a global switch (on/off). I don't know if that's too naive, but it should be possible to enable / disabling it by just changing the configuration (What I mean is, that there should be no need of changing the components) -- Ing. Leonardo Quijano Vincenzi DTQ Software Ron Piterman wrote: > While dojo seems a very good library, there are some serious > considerations about making tapestry really dependeant on it - > > I would like to know if that is going to be the case for 4.1... > > Well, as unpopular as it may sound, I find that very unacceptable - > dojo, as hip as it is, has also many disadvantages - like getting > really hard on the browser for very basic tasks - so page load time is > very long, getting high latency also when using top hardware - I don't > want to know what happens when and if using old browsers and hardware - > > I think if tapestry is heading the way of being a web framework for > ajax applications, not giving the basic sleek functionality for good > old web 1.0 - well - this requires some discussion from the community. > > currently, all JS is clean and functions well, I hope it stays that > way, *enabling* one to use JS libraries such as Dojo, but not > *imposing* one to use a certain one... > > Cheers, > Ron > > --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 14:39:27 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 71315 invoked from network); 1 Feb 2006 14:39:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 14:39:27 -0000 Received: (qmail 86739 invoked by uid 500); 1 Feb 2006 14:39:27 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 86433 invoked by uid 500); 1 Feb 2006 14:39:25 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 86422 invoked by uid 99); 1 Feb 2006 14:39:25 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO ajax.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 06:39:24 -0800 Received: from ajax.apache.org (ajax.apache.org [83.161.120.155]) by ajax.apache.org (Postfix) with ESMTP id B9FEAC9 for <johnsonbrian@example.com>; Wed, 1 Feb 2006 15:39:03 +0100 (CET) Message-ID: <johnsonbrian@example.com> Date: Wed, 1 Feb 2006 15:39:03 +0100 (CET) From: "Ron Piterman (JIRA)" <johnsonbrian@example.com> To: johnsonbrian@example.com Subject: [jira] Created: (TAPESTRY-850) Add a cycle scope to (abstract) properties MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Add a cycle scope to (abstract) properties ------------------------------------------ Key: TAPESTRY-850 URL: http://issues.apache.org/jira/browse/TAPESTRY-850 Project: Tapestry Type: Improvement Components: Framework Versions: 4.0.1 Reporter: Ron Piterman When letting tapestry set initialValue to a property, it currently sets the property on page load - If one uses an initial value that depends on parameter bindings, it all works fine, until the component is inside a loop and its bindings values are changing - please add a scope to initialValue to enable reset the property: instead on pageDetach enable resetting just before or just after the component renders. Thanx, Ron -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 14:54:04 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 80235 invoked from network); 1 Feb 2006 14:54:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 14:54:03 -0000 Received: (qmail 8815 invoked by uid 500); 1 Feb 2006 14:54:02 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 8801 invoked by uid 500); 1 Feb 2006 14:54:01 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 8790 invoked by uid 99); 1 Feb 2006 14:54:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 06:54:01 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of johnsonbrian@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ciao.gmane.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 06:54:00 -0800 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1F4JKt-0003mx-CH for johnsonbrian@example.com; Wed, 01 Feb 2006 15:51:56 +0100 Received: from d176234.adsl.hansenet.de ([83.161.120.155]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <johnsonbrian@example.com>; Wed, 01 Feb 2006 15:51:55 +0100 Received: from rpiterman by d176234.adsl.hansenet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <johnsonbrian@example.com>; Wed, 01 Feb 2006 15:51:55 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: johnsonbrian@example.com From: Ron Piterman <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts Date: Wed, 01 Feb 2006 15:50:53 +0100 Lines: 26 Message-ID: <johnsonbrian@example.com> References: <johnsonbrian@example.com> <254a01c62707$baec23d0$0101a8c0@norbi> <johnsonbrian@example.com> <johnsonbrian@example.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: johnsonbrian@example.com X-Gmane-NNTP-Posting-Host: d176234.adsl.hansenet.de User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) X-Accept-Language: en-us, en In-Reply-To: <johnsonbrian@example.com> Sender: news <johnsonbrian@example.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Leonardo Quijano Vincenzi wrote: > Dojo should be optional, IMO, but with a global switch (on/off). I don't > know if that's too naive, but it should be possible to enable / > disabling it by just changing the configuration (What I mean is, that > there should be no need of changing the components) > -1 on this integration. Are there any benefits beside enabling some ajax or effects magic ? I am also opposing integrating Tacos into Tapestry, but thats another thema... Instead of centralizing Tapestry - so good components come only from the main distribution, keep the libraries of components out there, like tacos is, make their life simple by joining development to make the support better, just like the case with Jesse is, but tapestry should stay a framework and not a solution, to the maximum extent abstract. e.g. : it should evolve to allow partial page rendering, making tacos life much easier, but keep the implementation of components to others, just like in the case of JSF... Cheers Ron --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 15:21:02 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 96535 invoked from network); 1 Feb 2006 15:21:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 15:21:02 -0000 Received: (qmail 67389 invoked by uid 500); 1 Feb 2006 15:21:01 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 67046 invoked by uid 500); 1 Feb 2006 15:21:00 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 67029 invoked by uid 99); 1 Feb 2006 15:21:00 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 07:21:00 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of johnsonbrian@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ws6-5.us4.outblaze.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 01 Feb 2006 07:20:58 -0800 Received: (qmail 8771 invoked from network); 1 Feb 2006 15:20:36 -0000 Received: from unknown (HELO ?83.161.120.155?) (johnsonbrian@example.com@83.161.120.155) by ws6-5.us4.outblaze.com with SMTP; 1 Feb 2006 15:20:36 -0000 Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <johnsonbrian@example.com> References: <johnsonbrian@example.com> <254a01c62707$baec23d0$0101a8c0@norbi> <johnsonbrian@example.com> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <johnsonbrian@example.com> Content-Transfer-Encoding: quoted-printable From: Jamie Orchard-Hays <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts Date: Wed, 1 Feb 2006 10:20:36 -0500 To: "Tapestry development" <johnsonbrian@example.com> X-Mailer: Apple Mail (2.746.2) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I'm curious how you would have components with integrated AJAX and =20 DHTML but have the javascript libraries they use as optional. And =20 what would the point be? If the components work why does it matter =20 what javascript library they use? People can always write their own =20 custom components with different javascript libraries if they want, =20 but I don't see any advantage to what you're suggesting. Jamie On Feb 1, 2006, at 6:22 AM, Ron Piterman wrote: > While dojo seems a very good library, there are some serious =20 > considerations about making tapestry really dependeant on it - > > I would like to know if that is going to be the case for 4.1... > > Well, as unpopular as it may sound, I find that very unacceptable - =20= > dojo, as hip as it is, has also many disadvantages - like getting =20 > really hard on the browser for very basic tasks - so page load time =20= > is very long, getting high latency also when using top hardware - I =20= > don't want to know what happens when and if using old browsers and =20 > hardware - > > I think if tapestry is heading the way of being a web framework for =20= > ajax applications, not giving the basic sleek functionality for =20 > good old web 1.0 - well - this requires some discussion from the =20 > community. > > currently, all JS is clean and functions well, I hope it stays that =20= > way, *enabling* one to use JS libraries such as Dojo, but not =20 > *imposing* one to use a certain one... > > Cheers, > Ron > > > > Norbert S=E1ndor wrote: >>> I agree that <service> was easier than the HM approach, which is >>> (infinitely) flexible. >> I think that the most perfect solution is if Hivemind supports =20 >> annotations therefore engine service implementations can define =20 >> their dependencies using annotations. (+ autowiring) >>> 1) Keep backwards compatibility and evolve the code base (give or =20= >>> take) >>> 2) Sacrifice backwards compatibility, but create the simpler, less >>> ambiguous (easier to learn) framework people want >> 2) >>> My current vision is that the 4.1 code base will be about =20 >>> creating new >>> components, including Ajax integration. Most of the innovation is >> Will 4.1 based on DOJO? (=3D Tacos and Tapestry 4 will be merged?) >> I think it is very important to fully support DOJO (now both =20 >> Tapestry and DOJO are stable): >> - some unified (documented) way to convert DOJO components to =20 >> Tapestry components >> - make them working in case of "partial" refresh >> - etc (more active dojo/tacos users may continue the list) >>> - Annotations based. JDK 1.5. >> Great, I would love generics in the API methods as well. =20 >> (Currently my code is full of warnings because of lack of java5 =20 >> support.) >>> - No XML for pages and components. Just HTML and Annotations. >> I don't like this, separating layout and component defs is a very =20 >> good thing in tapestry! >> I define components only in the .jwc/.page file, even in case of =20 >> the most simple RenderBody. And I think @Component is not a clean =20 >> solution especially when the component has many subcomponents, the =20= >> class file becomes "ugly". >>> ... others >> Great! >> Regards, >> Norbi > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: johnsonbrian@example.com > For additional commands, e-mail: johnsonbrian@example.com > --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 15:27:23 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 1796 invoked from network); 1 Feb 2006 15:27:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 15:27:22 -0000 Received: (qmail 75656 invoked by uid 500); 1 Feb 2006 15:27:22 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 75365 invoked by uid 500); 1 Feb 2006 15:27:20 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 75354 invoked by uid 99); 1 Feb 2006 15:27:20 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 07:27:20 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of johnsonbrian@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO xproxy.gmail.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 07:27:20 -0800 Received: by xproxy.gmail.com with SMTP id s9so116552wxc for <johnsonbrian@example.com>; Wed, 01 Feb 2006 07:26:59 -0800 (PST) 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:content-transfer-encoding:content-disposition:references; b=uuhtsc0RAJT8vs16API+LV2buJUgkS4NCZyaQUgsrdTrF7Hn0Bz2rOgPrTuWGQEeOI9O7IHnQcCLwbMoL6oSbBjSbrUtC+vAZc0TA9yIIJ6PPjZo0HXz1fPsPMuM+xPpF6C9A2hVhwRrzw27VnFbLM+ACQj3qIGgqGsWxaQl9h0= Received: by 83.161.120.155 with SMTP id b4mr786684wxb; Wed, 01 Feb 2006 07:26:59 -0800 (PST) Received: by 83.161.120.155 with HTTP; Wed, 1 Feb 2006 07:26:59 -0800 (PST) Message-ID: <johnsonbrian@example.com> Date: Wed, 1 Feb 2006 10:26:59 -0500 From: Geoff Longman <johnsonbrian@example.com> To: Tapestry development <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts In-Reply-To: <johnsonbrian@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <johnsonbrian@example.com> <254a01c62707$baec23d0$0101a8c0@norbi> <johnsonbrian@example.com> <johnsonbrian@example.com> <johnsonbrian@example.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Yes I think that the framework should make doing Ajax easier (partial rendering of pages) but tying the framework to dojo is a bad idea. That said, there is an avenue for Tacos to come into the fold, it's called the contrib library. In there it can bring dojo along too. Geoff On 2/1/06, Ron Piterman <johnsonbrian@example.com> wrote: > Leonardo Quijano Vincenzi wrote: > > Dojo should be optional, IMO, but with a global switch (on/off). I don'= t > > know if that's too naive, but it should be possible to enable / > > disabling it by just changing the configuration (What I mean is, that > > there should be no need of changing the components) > > > > -1 on this integration. > > Are there any benefits beside enabling some ajax or effects magic ? > > I am also opposing integrating Tacos into Tapestry, but thats another > thema... > > Instead of centralizing Tapestry - so good components come only from the > main distribution, keep the libraries of components out there, like > tacos is, make their life simple by joining development to make the > support better, just like the case with Jesse is, but tapestry should > stay a framework and not a solution, to the maximum extent abstract. > > e.g. : it should evolve to allow partial page rendering, making tacos > life much easier, but keep the implementation of components to others, > just like in the case of JSF... > > Cheers > Ron > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: johnsonbrian@example.com > For additional commands, e-mail: johnsonbrian@example.com > > -- The Spindle guy. http://spindle.sf.net Get help with Spindle: =20 http://lists.sourceforge.net/mailman/listinfo/spindle-user Blog: http://jroller.com/page/glongman Feature Updates: http://spindle.sf.net/updates --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 15:53:35 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 18080 invoked from network); 1 Feb 2006 15:53:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 15:53:34 -0000 Received: (qmail 35881 invoked by uid 500); 1 Feb 2006 15:53:29 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 35838 invoked by uid 500); 1 Feb 2006 15:53:29 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 35786 invoked by uid 99); 1 Feb 2006 15:53:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 07:53:29 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [83.161.120.155] (HELO ns.dtqsoftware.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 07:53:24 -0800 Received: (qmail 23297 invoked from network); 1 Feb 2006 10:52:58 -0500 Received: from softdnserror (HELO ?83.161.120.155?) (83.161.120.155) by tor149-99-23-135.dedicated.sprintdsl.ca with SMTP; 1 Feb 2006 10:52:58 -0500 Message-ID: <johnsonbrian@example.com> Date: Wed, 01 Feb 2006 09:52:50 -0600 From: Leonardo Quijano Vincenzi <johnsonbrian@example.com> User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Tapestry development <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts References: <johnsonbrian@example.com> <254a01c62707$baec23d0$0101a8c0@norbi> <johnsonbrian@example.com> <johnsonbrian@example.com> <johnsonbrian@example.com> In-Reply-To: <johnsonbrian@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 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Totally -1 on having lots of distributed libraries, like Tassel. "Community support" they call it but it's really a ton of unsupported, buggy components that could be better done under a couple of large libraries. Now, I haven't said "Integrate Dojo with Tapestry". I'm talking about component composition, Javascript and Ajax support should be added like Tapestry currently does with validators, in an optional way. What's the point of having a TextField and a separate Autocompleter component ? Why don't add the autocomplete functionality to an existing TextField with a render contribution? That's orthogonality and it's something Tapestry is lacking. It doesn't mean it has to be on the main codebase. It could be in the contrib project (what's the point of the current Contrib ?? why aren't those components in the core?). Actually I'm +1 on having a Tapestry-Core and a Tapestry-Components base. Plus Tapestry-Annotations and Tapestry-Portlets. Tapestry-Components would have standard components with optional Ajax bindings. I don't know if that's too hard to design, but from a developer point of view is far easier to turn a switch on than to change all textfields in your application just because someone is still making "Web 1.0" apps. > e.g. : it should evolve to allow partial page rendering, making tacos > life much easier, but keep the implementation of components to others, > just like in the case of JSF... One of the main strengths of Tapestry, IMO, is that it always had a very strong core components base. Delegating the implementation to third parties would start the JSF syndrome: a very "powerful" core framework, no useful components (so I tried using JSF six months ago and couldn't find a Table component that allowed for radio button selections!). That can change later, but then we have several uncompatible third-party libraries ("I have this on X, that on Y, but nobody gives me all!") I repeat, *it doesn't have to be in the core*. Moreover, I think the core should have no components! That would be done in Tapestry-Components, as I said. It could even have different committers, or whatever... -- Ing. Leonardo Quijano Vincenzi DTQ Software --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 15:53:47 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 18323 invoked from network); 1 Feb 2006 15:53:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 15:53:46 -0000 Received: (qmail 37506 invoked by uid 500); 1 Feb 2006 15:53:44 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 37493 invoked by uid 500); 1 Feb 2006 15:53:44 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 37482 invoked by uid 99); 1 Feb 2006 15:53:44 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 07:53:44 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of johnsonbrian@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ciao.gmane.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 07:53:43 -0800 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1F4KI1-0004HW-27 for johnsonbrian@example.com; Wed, 01 Feb 2006 16:53:02 +0100 Received: from d176234.adsl.hansenet.de ([83.161.120.155]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <johnsonbrian@example.com>; Wed, 01 Feb 2006 16:53:01 +0100 Received: from rpiterman by d176234.adsl.hansenet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <johnsonbrian@example.com>; Wed, 01 Feb 2006 16:53:01 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: johnsonbrian@example.com From: Ron Piterman <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts Date: Wed, 01 Feb 2006 16:52:32 +0100 Lines: 116 Message-ID: <johnsonbrian@example.com> References: <johnsonbrian@example.com> <254a01c62707$baec23d0$0101a8c0@norbi> <johnsonbrian@example.com> <johnsonbrian@example.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: johnsonbrian@example.com X-Gmane-NNTP-Posting-Host: d176234.adsl.hansenet.de User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) X-Accept-Language: en-us, en In-Reply-To: <johnsonbrian@example.com> Sender: news <johnsonbrian@example.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Jamie Orchard-Hays wrote: > I'm curious how you would have components with integrated AJAX and > DHTML but have the javascript libraries they use as optional. You just don't. I do understand why poeple want tacos to come into tapestry, maybe in the contrib library, but I don't think its the right thing for tapestry to do. Why do this merge? is it just in one line with the HLS centralizing - making also the tapestry framework home for all high quality components? IMO its important that tacos stays there as tacos, thats it reaches maturity on its own, and that it interacts (and jesse will sureley take care of that...) , but does not merge into the codebase of tapestry. Ofcause, the middle way could be, after tapestry is an direct Apache project, add an Ajax subproject with all kind of firework and music. It is also a sign of a framework evolvement - that many different independant "repositories" are contributing to it - Cheers, Ron And what > would the point be? If the components work why does it matter what > javascript library they use? People can always write their own custom > components with different javascript libraries if they want, but I > don't see any advantage to what you're suggesting. > > Jamie > > > On Feb 1, 2006, at 6:22 AM, Ron Piterman wrote: > >> While dojo seems a very good library, there are some serious >> considerations about making tapestry really dependeant on it - >> >> I would like to know if that is going to be the case for 4.1... >> >> Well, as unpopular as it may sound, I find that very unacceptable - >> dojo, as hip as it is, has also many disadvantages - like getting >> really hard on the browser for very basic tasks - so page load time >> is very long, getting high latency also when using top hardware - I >> don't want to know what happens when and if using old browsers and >> hardware - >> >> I think if tapestry is heading the way of being a web framework for >> ajax applications, not giving the basic sleek functionality for good >> old web 1.0 - well - this requires some discussion from the community. >> >> currently, all JS is clean and functions well, I hope it stays that >> way, *enabling* one to use JS libraries such as Dojo, but not >> *imposing* one to use a certain one... >> >> Cheers, >> Ron >> >> >> >> Norbert Sándor wrote: >> >>>> I agree that <service> was easier than the HM approach, which is >>>> (infinitely) flexible. >>> >>> I think that the most perfect solution is if Hivemind supports >>> annotations therefore engine service implementations can define >>> their dependencies using annotations. (+ autowiring) >>> >>>> 1) Keep backwards compatibility and evolve the code base (give or >>>> take) >>>> 2) Sacrifice backwards compatibility, but create the simpler, less >>>> ambiguous (easier to learn) framework people want >>> >>> 2) >>> >>>> My current vision is that the 4.1 code base will be about creating new >>>> components, including Ajax integration. Most of the innovation is >>> >>> Will 4.1 based on DOJO? (= Tacos and Tapestry 4 will be merged?) >>> I think it is very important to fully support DOJO (now both >>> Tapestry and DOJO are stable): >>> - some unified (documented) way to convert DOJO components to >>> Tapestry components >>> - make them working in case of "partial" refresh >>> - etc (more active dojo/tacos users may continue the list) >>> >>>> - Annotations based. JDK 1.5. >>> >>> Great, I would love generics in the API methods as well. (Currently >>> my code is full of warnings because of lack of java5 support.) >>> >>>> - No XML for pages and components. Just HTML and Annotations. >>> >>> I don't like this, separating layout and component defs is a very >>> good thing in tapestry! >>> I define components only in the .jwc/.page file, even in case of the >>> most simple RenderBody. And I think @Component is not a clean >>> solution especially when the component has many subcomponents, the >>> class file becomes "ugly". >>> >>>> ... others >>> >>> Great! >>> Regards, >>> Norbi >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: johnsonbrian@example.com >> For additional commands, e-mail: johnsonbrian@example.com >> --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 16:10:47 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 27501 invoked from network); 1 Feb 2006 16:10:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 16:10:47 -0000 Received: (qmail 87378 invoked by uid 500); 1 Feb 2006 16:10:45 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 87354 invoked by uid 500); 1 Feb 2006 16:10:44 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 87342 invoked by uid 99); 1 Feb 2006 16:10:44 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 08:10:44 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of johnsonbrian@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ciao.gmane.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 08:10:42 -0800 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1F4KXg-0000LS-NM for johnsonbrian@example.com; Wed, 01 Feb 2006 17:09:13 +0100 Received: from d176234.adsl.hansenet.de ([83.161.120.155]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <johnsonbrian@example.com>; Wed, 01 Feb 2006 17:09:12 +0100 Received: from rpiterman by d176234.adsl.hansenet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <johnsonbrian@example.com>; Wed, 01 Feb 2006 17:09:12 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: johnsonbrian@example.com From: Ron Piterman <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts Date: Wed, 01 Feb 2006 17:09:39 +0100 Lines: 66 Message-ID: <johnsonbrian@example.com> References: <johnsonbrian@example.com> <254a01c62707$baec23d0$0101a8c0@norbi> <johnsonbrian@example.com> <johnsonbrian@example.com> <johnsonbrian@example.com> <johnsonbrian@example.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: johnsonbrian@example.com X-Gmane-NNTP-Posting-Host: d176234.adsl.hansenet.de User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) X-Accept-Language: en-us, en In-Reply-To: <johnsonbrian@example.com> Sender: news <johnsonbrian@example.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Leonardo Quijano Vincenzi wrote: > Totally -1 on having lots of distributed libraries, like Tassel. > "Community support" they call it but it's really a ton of unsupported, > buggy components that could be better done under a couple of large > libraries. > > Now, I haven't said "Integrate Dojo with Tapestry". I'm talking about > component composition, Javascript and Ajax support should be added like > Tapestry currently does with validators, in an optional way. What's the > point of having a TextField and a separate Autocompleter component ? Why > don't add the autocomplete functionality to an existing TextField with a > render contribution? :) currently TextField has 7 parameters. know how many autocompleter has? 13 !, yes 13 ! now thats a fine component for the tapestry code base :) > > That's orthogonality and it's something Tapestry is lacking. It doesn't > mean it has to be on the main codebase. It could be in the contrib > project (what's the point of the current Contrib ?? why aren't those > components in the core?). Actually I'm +1 on having a Tapestry-Core and > a Tapestry-Components base. Plus Tapestry-Annotations and > Tapestry-Portlets. > > Tapestry-Components would have standard components with optional Ajax > bindings. I don't know if that's too hard to design, but from a > developer point of view is far easier to turn a switch on than to change > all textfields in your application Maybe I got this wrong, but is that not the idea of a component? to encapsulate functionality - so you want other or additional functionality, you use another component - Or should TextField be there for all-use-cases-what-so-ever and there be no other text field component on earth? Keep it small and functional, deliver the basic functionality, and not the swissknife "can-do-everything-but-just-almost" - ever tried to actually use the saw in a swiss knife? Now when you decide to use ajax - do you "change all textfields in your application" ? sure if you use it for each and every input. good luck with it then... :) >just because someone is still making > "Web 1.0" apps. > >> e.g. : it should evolve to allow partial page rendering, making tacos >> life much easier, but keep the implementation of components to others, >> just like in the case of JSF... > > One of the main strengths of Tapestry, IMO, is that it always had a very > strong core components base. Delegating the implementation to third > parties would start the JSF syndrome: a very "powerful" core framework, > no useful components (so I tried using JSF six months ago and couldn't > find a Table component that allowed for radio button selections!). That > can change later, but then we have several uncompatible third-party > libraries ("I have this on X, that on Y, but nobody gives me all!") > > I repeat, *it doesn't have to be in the core*. Moreover, I think the > core should have no components! That would be done in > Tapestry-Components, as I said. It could even have different committers, > or whatever... > --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 16:27:15 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 39883 invoked from network); 1 Feb 2006 16:27:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 16:27:14 -0000 Received: (qmail 26227 invoked by uid 500); 1 Feb 2006 16:27:12 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 26214 invoked by uid 500); 1 Feb 2006 16:27:12 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 26203 invoked by uid 99); 1 Feb 2006 16:27:12 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 08:27:12 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [83.161.120.155] (HELO ns.dtqsoftware.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 08:27:12 -0800 Received: (qmail 26813 invoked from network); 1 Feb 2006 11:26:48 -0500 Received: from softdnserror (HELO ?83.161.120.155?) (83.161.120.155) by tor149-99-23-135.dedicated.sprintdsl.ca with SMTP; 1 Feb 2006 11:26:48 -0500 Message-ID: <johnsonbrian@example.com> Date: Wed, 01 Feb 2006 10:26:38 -0600 From: Leonardo Quijano Vincenzi <johnsonbrian@example.com> User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Tapestry development <johnsonbrian@example.com> Subject: Re: Tapestry 5 thoughts References: <johnsonbrian@example.com> <254a01c62707$baec23d0$0101a8c0@norbi> <johnsonbrian@example.com> <johnsonbrian@example.com> <johnsonbrian@example.com> <johnsonbrian@example.com> <johnsonbrian@example.com> In-Reply-To: <johnsonbrian@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 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N You're getting me wrong. You're talking about monolithic components, I'm talking about component composition. I don't know what's the *best* way of doing this, design-wise, so please don't jump in conclusions. I'm talking about why Ajaxcompleter has the Textfield functionality copied. So, instead of having 2 TextFields, one with standard functionality, and one with autocomplete, we'd have some "component parts", or whatever you should call it, that we "compose" together and build a full featured TextField with 30+ functions. It's not that the base component has 30+ functions. Is the *composition* of components that has it. Aren't validators and translators pluggable ? Why don't do the same with Ajax?? Tacos is already doing it, I'm just talking about making it official. -- Ing. Leonardo Quijano Vincenzi DTQ Software --------------------------------------------------------------------- To unsubscribe, e-mail: johnsonbrian@example.com For additional commands, e-mail: johnsonbrian@example.com From tapestry-dev-returnjohnsonbrian@example.com Wed Feb 01 16:37:43 2006 Return-Path: <tapestry-dev-returnjohnsonbrian@example.com> Delivered-To: johnsonbrian@example.com Received: (qmail 44351 invoked from network); 1 Feb 2006 16:37:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2006 16:37:43 -0000 Received: (qmail 48573 invoked by uid 500); 1 Feb 2006 16:37:42 -0000 Delivered-To: johnsonbrian@example.com Received: (qmail 48383 invoked by uid 500); 1 Feb 2006 16:37:41 -0000 Mailing-List: contact johnsonbrian@example.com; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:johnsonbrian@example.com> List-Help: <mailto:johnsonbrian@example.com> List-Post: <mailto:johnsonbrian@example.com> List-Id: "Tapestry development" <tapestry-dev.jakarta.apache.org> Reply-To: "Tapestry development" <johnsonbrian@example.com> Delivered-To: mailing list johnsonbrian@example.com Received: (qmail 48372 invoked by uid 99); 1 Feb 2006 16:37:41 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2006 08:37:41 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of johnsonbrian@example.com designates 83.161.120.155 as
{'source': 'Apache Software Foundation Public Mail Archives'}