tapestry-contrib Mailing List for Tapestry: Java Web Components
Brought to you by:
hship
Menu
▾
▴
tapestry-contrib — List for Tapestry contributors to discuss action items and to perform voting
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(113) |
Dec
(153) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(80) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(3) |
Dec
|
|
From: Geoff L. <glo...@in...> - 2003-11-26 12:59:39
|
Vitalily, As Tapestry has moved to Jakarta, this list is dead. You should repost your problem on the new list. mailto:tap...@ja... Cheers, Geoff ----- Original Message ----- From: "Vitaliy Ryumshyn" <ru...@we...> To: <tap...@li...> Sent: Wednesday, November 26, 2003 7:53 AM Subject: [Tapestry-contrib] Frame component problem Hi I tried to use @Frame component but it does not work by me. No errors or messages,in log file I see that PageLoader loads all pages but in result main page (with frameset) has no frame. Snapshot from result rendered page: <frameset cols="70%,30%" frameborder="YES" border="1" framespacing="5"> <frame src="/tspd/app?service=page/TsResultFrameLeft" scrolling="AUTO"/> <frame src="/tspd/app?service=page/TsResultFrameRight" scrolling="AUTO"/> </frameset> Why it did not include these pages? Could anyone give me some example of using this component? PS. Version 3.0b3 Thank you in advance., Vitali |
|
From: Vitaliy R. <ru...@we...> - 2003-11-26 12:54:05
|
Hi I tried to use @Frame component but it does not work by me. No errors or = messages,in log file I see that PageLoader loads all pages but in result main page (with frameset) has no frame. Snapshot from result rendered page: <frameset cols=3D"70%,30%" frameborder=3D"YES" border=3D"1" = framespacing=3D"5"> <frame src=3D"/tspd/app?service=3Dpage/TsResultFrameLeft" = scrolling=3D"AUTO"/> <frame src=3D"/tspd/app?service=3Dpage/TsResultFrameRight" = scrolling=3D"AUTO"/> </frameset> Why it did not include these pages? Could anyone give me some example of using this component? PS. Version 3.0b3 Thank you in advance., Vitali |
|
From: Vitaliy R. <ru...@we...> - 2003-11-26 12:45:39
|
Hi, I'm new in Tapestry and have faced a one problem: I have a one select component in my template it uses @Foreach and = @Options components to produce my multiselect element, everythings is Ok, but I cannot manage the = values attributes of option element, it always generate numeric values: <select name=3D"$Select" multiple=3D"multiple"> <option value=3D"0">Test1</option> <option value=3D"1">Test2</option> <option value=3D"2">Test3</option> but I need for example: <select name=3D"$Select" multiple=3D"multiple"> <option value=3D"T1">Test1</option> <option value=3D"T2">Test2</option> <option value=3D"T3">Test3</option> Using PropertySelection allows to connect IPropertySelectionModel and = manage values, but not in multiple select... Is there the right way to do what I want? Best Regards, Vitali |
|
From: Kris R. <kri...@ya...> - 2003-09-11 09:55:26
|
confirm 558135 --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software |
|
From: Kris R. <kri...@ya...> - 2003-09-11 09:54:11
|
It would be extremely usefull if it was possible to change the html template used for a page or component, for example based on the url used to access it (could be configured in the web deployment descriptor). My reason for doing so is a special case, however I beleive it would be useful for example if you wanted to have a pocket pc version of the site. There are many other uses as well obviously. Please let me know if this is possible already! Kris Rasmussen --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software |
|
From: tsvetelin <tsv...@ru...> - 2003-08-22 15:00:49
|
Hi Tomas, I have made a little mistake in my previous email. If would like to implement your own page that shows the application runtime errors you should define a method "public void setException(Throwable ex);" Tzvetelin -----Original Message----- Hi Tomas, First the Tapestry project was moved to Jakarta and this mailing list is closed. Please register to tapestry mailing list on Jakarta. You could specify the error page in your web application if you define a page in you *.application file called "Exception" that must have a method "public void exception(Throwable ex);", so the default page will be skipped. Please see IEngine.EXCEPTION_PAGE for more details. From my point of view the ApplicationRuntimeException will be receive in 2 cases. The 1 one is when there is something wrong in implementation of application structure(like wring page/component definition) and the second one when there occur internal server errors. In the most 2 cases from design point of view it is good idea to catch the second case in your code so I think that in a real live application you will not receive this exception. -----Original Message----- From: tap...@li... [mailto:tap...@li...]On Behalf Of Thomas Sent: Thursday, August 21, 2003 1:25 PM To: tap...@li... Subject: [Tapestry-contrib] How to turn off error reporting? Hi, folks! I really like the error reporting feature very much. But on a live website this is a huge security risk. How can I turn it off? For example, org.apache.tapestry.ApplicationRuntimeException error is displayed often. I use the lastest, Apache 3 beta 2 version. Thanks for your help! Thomas Derflinger |
|
From: Thomas <ne...@gm...> - 2003-08-22 10:35:24
|
Hi, folks! I really like the error reporting feature very much. But on a live website this is a huge security risk. How can I turn it off? For example, org.apache.tapestry.ApplicationRuntimeException error is displayed often. I use the lastest, Apache 3 beta 2 version. Thanks for your help! Thomas Derflinger |
|
From: Lennart B. <Len...@as...> - 2003-07-02 15:12:31
|
Hey Guys, Soon i wil start porting a large tapestry application in 2.3 to 3.0. I=20 don't seem to find a porting / upgrading howto. Would the community be=20 interested in such a document? I'm prepared to make such a document / or=20 contribute my expieriences. Regards, Lennart |
|
From: <sup...@gm...> - 2003-05-28 12:53:20
|
I would like to download the "Tapestry Component Reference". Is there zipped download version? Toby -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! |
|
From: Emiliano H. <em...@ir...> - 2003-03-03 23:10:35
|
Hi all, I'm currently investigating toolkits for my web project, and Tapestry looks like a nice approach. The one thing that I haven't been able to figure out from the docs: is it possible to createparts of the user interface dynamically? My intended app will decide for parts of its user interface what type and number of controls to display based on data from a database. So far, I could only find ways to do static controls (as directed by the templates) or data insertion. Emile |
|
From: Sriram I. <sri...@ur...> - 2003-02-24 01:16:23
|
Hi there,
I'm trying to use the visit object in my login page. However,
I keep getting a compile error when I invoke the getVisit
method. I'm not sure why I am getting it. Attached is the
source code. Please advise.
--sri
compile:
[javac] Compiling 1 source file to
C:\cvsroot\ecms\new\ecms\ecms.war\WEB-INF
\classes
[javac]
C:\cvsroot\ecms\new\ecms\src\ecms\web\Home.java:150: cannot
resolve
symbol
[javac] symbol : class Visit
[javac] location: class ecms.web.Home
[javac] Visit visit = (Visit)getPage().getVisit
();;
[javac] ^
[javac]
C:\cvsroot\ecms\new\ecms\src\ecms\web\Home.java:150: cannot
resolve
symbol
[javac] symbol : class Visit
[javac] location: class ecms.web.Home
[javac] Visit visit = (Visit)getPage().getVisit
();;
[javac] ^
[javac] 2 errors
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag |
|
From: Howard M. L. S. <hl...@at...> - 2003-01-21 12:02:19
|
As you all probably know, Tapestry is in transition, moving to the = Jakarta project. This is a gradual process, happening in fits and = starts. Shortly, the SourceForge mailing lists will be shut down. New mailing = lists for Tapestry are available at Jakarta: http://jakarta.apache.org/site/mail.html tap...@ja... is the general mailing list, used for = discussions on how to use Tapestry tap...@ja... is the developer's mailing list, used by = the Tapestry crew to discuss bug fixes, extensions and such Within a couple of weeks, I will no longer be monitoring the two lists = on SourceForge. For the moment, I'm cross-posting replies to both = lists. The best thing everyone can do is to unsubscribe from the = SourceForge lists and subscribe to the Jakarta lists. ---- Howard Lewis Ship hl...@at... http://jakarta.apache.org/proposals/tapestry |
|
From: Neil C. <ne...@cl...> - 2003-01-16 07:21:04
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 +1 On Wednesday 15 Jan 2003 11:55 am, Howard M. Lewis Ship wrote: > Ok, we've discussed putting 2.3 "to bed". 2.3 beta-1 has been out ther= e > for a bit, I've even seen comments that it was stable and easy to upgra= de. > > The final major changethe addition of the "Global" mechanism, a counter= part > to the "Visit" mechanism, except that the global property is shared by = all > engines in the application. In addition, all source code now has the b= ig, > ugly Apache license comment block. > > Plan: > 1) Create a branch off of HEAD for 2.3 > 2) Label and create a release for 2.3-rc-1 > 3) Merge private branch changes back into HEAD > 4) Rename packages and reorganize directory structure > > If any bugs to pop up in 2.3-rc-1, we'll fix them in its branch, and in > HEAD. I don't see too much along those lines. > > Also, is everyone subscribed to the NEW list?=20 > tap...@ja... > > ---- > Howard Lewis Ship > hl...@at... > http://tapestry.sf.net - --=20 Regards, Neil Clayton (PS: If you see strange text you don't understand underneath my email, do= n't=20 worry - it's just my PGP signature) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Jl4gLXcfQF3yrNoRAuSuAJ49oBxHJV2Oq+q9biuwKqqnC5wBAQCeJ7qn FTs6W4aXK2gz3yF6quH0dbE=3D =3D2We1 -----END PGP SIGNATURE----- |
|
From: Malcolm E. <ma...@tp...> - 2003-01-15 12:47:43
|
Malcolm Edgar: +1 There is a bug with the build.xml target "deploy-tomcat" in that it doesn't copy the /lib/ext/ejb.jar across to web lib. This causes the Tapestry Tutorial Inspector Engine page to crash when running under Tomcat. Also the Readme.html "Third party JARs" needs to be updated to include: commons-lang, commons-logging & junit. I have just subscribed to the new list. regards Malcolm At 06:55 AM 15/01/2003 -0500, Howard M. Lewis Ship wrote: >Ok, we've discussed putting 2.3 "to bed". 2.3 beta-1 has been out there >for a bit, I've even seen comments that it was stable and easy to upgrade. > >The final major changethe addition of the "Global" mechanism, a >counterpart to the "Visit" mechanism, except that the global property is >shared by all engines in the application. In addition, all source code >now has the big, ugly Apache license comment block. > >Plan: >1) Create a branch off of HEAD for 2.3 >2) Label and create a release for 2.3-rc-1 >3) Merge private branch changes back into HEAD >4) Rename packages and reorganize directory structure > >If any bugs to pop up in 2.3-rc-1, we'll fix them in its branch, and in >HEAD. I don't see too much along those lines. > >Also, is everyone subscribed to the NEW >list? <mailto:tap...@ja...>tap...@ja... > >---- >Howard Lewis Ship ><mailto:hl...@at...>hl...@at... >http://tapestry.sf.net |
|
From: Geoff L. <glo...@in...> - 2003-01-15 12:07:38
|
>Plan: >1) Create a branch off of HEAD for 2.3 >2) Label and create a release for 2.3-rc-1 >3) Merge private branch changes back into HEAD >4) Rename packages and reorganize directory structure +1 >Also, is everyone subscribed to the NEW list? tap...@ja... +1 Geoff Geoffrey Longman Intelligent Works Inc. |
|
From: Howard M. L. S. <hl...@at...> - 2003-01-15 11:58:02
|
Ok, we've discussed putting 2.3 "to bed". 2.3 beta-1 has been out there = for a bit, I've even seen comments that it was stable and easy to = upgrade. The final major changethe addition of the "Global" mechanism, a = counterpart to the "Visit" mechanism, except that the global property is = shared by all engines in the application. In addition, all source code = now has the big, ugly Apache license comment block. Plan: 1) Create a branch off of HEAD for 2.3 2) Label and create a release for 2.3-rc-1 3) Merge private branch changes back into HEAD 4) Rename packages and reorganize directory structure If any bugs to pop up in 2.3-rc-1, we'll fix them in its branch, and in = HEAD. I don't see too much along those lines. Also, is everyone subscribed to the NEW list? = tap...@ja...=20 ---- Howard Lewis Ship hl...@at... http://tapestry.sf.net |
|
From: Geoff L. <glo...@in...> - 2003-01-14 13:56:18
|
http://tapestry.sourceforge.net/wiki/index.php/CodebaseReorg comments, suggestions are welcome Geoff Geoffrey Longman Intelligent Works Inc. |
|
From: Andrew C. O. <aco...@ap...> - 2003-01-13 12:59:20
|
Okay...well if this is going to take awhile... you might want to: A. check the web pages into CVS so my site script can check them out and publish them B. check the version of ant you're using into CVS and provide a shell script to launch the build with that version of ant so that my site script can check them out and publish them. I'd like to get the website migrated over soon as I may not have as much time shortly. -Andy Howard M. Lewis Ship wrote: > I just want to caution against one thing: Please do not reoganize the > source code directories yet. I know we want to organize the project > structure more like an Apache project and that's fine ... but to do so now > would cripple my ability to cleanly and safely merge in a huge number of > changes from my branch and Mind Bridge is in the same boat with his branch. > > Once we put 2.3 to bed, we can merge in code changes into 2.4 and then we > can rename packages and reorganize overall structure. > > ----- Original Message ----- > From: "Howard M. Lewis Ship" <hl...@at...> > To: "Tapestry development" <tap...@ja...> > Cc: <tap...@li...>; > <tap...@ja...> > Sent: Monday, January 13, 2003 7:09 AM > Subject: Re: [Tapestry-contrib] Getting back into it > > > >>To help with Maven, here's some notes about how releases are currently >>built. Some of these notes overlap details in the Contributor's Guide, so >>you should check that out as well. >> >>The master build file does all the work, reinvoking Ant in many >>subdirectories and combining all the results. >> >>I've seen a lot of projects that require you to set environment variables >>and/or use a shell script wrapper. I don't get why. >> >>The only thing external to the Tapestry workspace is the directories for a >>couple of large, external tools: JBoss, FOP, Saxon and Clover. >> >>JBoss is needed because we build demos that plug into JBoss in a turnkey >>way. FOP is for DocBook to PDF. Saxon is for DocBook to HTML or DocBook > > to > >>Flow Objects (fed into FOP) ... I use Saxon because it is about 20x faster >>than Xalan doing the same job. Clover is proprietary source code coverage >>tool. >> >>Getting Ant to use Saxon instead of Xalan requires a few command line >>options that can be accomplished via the ANT_OPTS env variable: >> >> > > ANT_OPTS=-Xmx256mb -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.cri > > son.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=o > >>rg.apache.crimson.jaxp.SAXParserFactoryImpl >> >>The other three external tools (JBoss, FOP and Clover) are identified in > > the > >>build.properties file which must be placed into the config directory. > > This > >>file sets three properties needed by the many Ant build scripts: >> >>jboss.dir >>fop.dir >>clover.dir >> >>Each of these is the absolute path to the respective tool. It is > > important > >>to use FORWARD SLASHES ONLY or you will get build errors. I've enclosed a >>copy that I use when I do builds. >> >>Clover has kindly donated a copy of their tool to Tapestry; a copy of > > their > >>distribution is in the support directory. >> >>The final piece of the puzzle is the disto build script. This is in the >>support directory. I typically copy this out to a temporary directory. I >>also copy my current build.properties file to the same directory. >> >>The distro build script has two targets. "setup" uses anonymous CVS to > > grab > >>a fresh copy of the Tapestry workspace. It uses export, so that the CVS >>directories are not exported. This takes about one minute. >> >>"build" copies the build.properties file into the exported workspace and >>invokes the "dist" target on the master build file. It then copies the >>resulting distro files back up to the current directory. This takes about >>nine minutes (on my new, blazing fast laptop, anyway). >> >>Side note: Tapestry has, checked into the repository, copies of DocBook > > XML > >>and the DocBook XSL distros. It automatically unpacks these as needed >>during the build. We may want to change things to make these addtiional, >>external tools as well. >> >>Side note: People have had compatibility issues when using Tapestry JARs >>compiled by the 1.4 compiler, even in 1.3 compatibility mode. I currently >>set my JAVA_HOME to a JDK 1.3 before doing the build to ensure maximum >>compatibility. >> >>Currently, three distro files are created: Tapestry-x.x-core.tar.gz is > > the > >>main distribution, containing the compiled JARs, external libraries (such > > as > >>OGNL and Log4J) and the source code (packaged into .jar files). >> >>Tapestry-x.x.-doc.tar.gz contains all the documentation for Tapestry; >>JavaDoc, Contributor's Guide, and the various manuals (in HTML and PDF). >> >>Tapestry-Web-x.x.tar.gz contains an image of the Tapestry web site, which > > is > >>similar to the doc distro, but includes the Clover code coverage report. >> >>Tapestry builds .tar.gz files currently because a) WinZip can open them > > fine > >>and b) they are smaller than the equivalent .zip files. >> >>I'm sure there'll be some impedance using Maven, but since Tapestry is >>already built to use straight Ant to perform full builds (albiet with a >>couple of configuration gotchas) I hope it will not be too tricky. >> >>----- Original Message ----- >>From: <di...@mu...> >>To: "Andrew C. Oliver" <aco...@ap...> >>Cc: <tap...@li...>; >><tap...@ja...> >>Sent: Monday, January 13, 2003 4:07 AM >>Subject: Re: [Tapestry-contrib] Getting back into it >> >> >> >>>tap...@li... wrote on 13/01/2003 >> > 09:07:03 > >>>AM: >>> >>>>I really recommend Mavenizing to this effect. I bet dion would help >>>>with that.. (http://jakarta.apache.org/maven) >>> >>>I'm happy to help with Mavenizing, if only for the docs part of the >>>process. We should also look and see if we can improve the docbook >> > plugin > >>>for Maven (as it's rarely used and a little buggy!), to handle the >>>existing formats. >>> >>> >>>>Alternatively (and this is what POI does) if maven doesn't do what you >>>>need Centipede (http://krysalis.org/centipede) and Forrest >>>>(http://xml.apache.org/forrest) might help. >>>> >>>>However it really depends on whether Maven works under gump... >>> >>>Maven generates viable gump descriptors these days. >>> >>> >>>>Gump should be one of our top priorities (jakarta.apache.org/gump) >>>>because it could do the builds and site publish for us... >>> >>>+1 >>>-- >>>dIon Gillard, Multitask Consulting >>>Blog: http://www.freeroller.net/page/dion/Weblog >>>Work: http://www.multitask.com.au >>> >>> >>> >>> >>>-- >>>To unsubscribe, e-mail: >> >><mailto:tap...@ja...> >> >>>For additional commands, e-mail: >> >><mailto:tap...@ja...> >> >>> > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Tapestry-contrib mailing list > Tap...@li... > https://lists.sourceforge.net/lists/listinfo/tapestry-contrib > |
|
From: Geoff L. <glo...@in...> - 2003-01-13 12:56:46
|
Understood. I'm just going to research the change for now. Geoff ----- Original Message ----- From: "Howard M. Lewis Ship" <hl...@at...> To: "Tapestry development" <tap...@ja...> Cc: <tap...@li...>; <tap...@ja...> Sent: Monday, January 13, 2003 7:45 AM Subject: Maven .... Nightmare > I just want to caution against one thing: Please do not reoganize the > source code directories yet. I know we want to organize the project > structure more like an Apache project and that's fine ... but to do so now > would cripple my ability to cleanly and safely merge in a huge number of > changes from my branch and Mind Bridge is in the same boat with his branch. > > Once we put 2.3 to bed, we can merge in code changes into 2.4 and then we > can rename packages and reorganize overall structure. > > ----- Original Message ----- > From: "Howard M. Lewis Ship" <hl...@at...> > To: "Tapestry development" <tap...@ja...> > Cc: <tap...@li...>; > <tap...@ja...> > Sent: Monday, January 13, 2003 7:09 AM > Subject: Re: [Tapestry-contrib] Getting back into it > > > > To help with Maven, here's some notes about how releases are currently > > built. Some of these notes overlap details in the Contributor's Guide, so > > you should check that out as well. > > > > The master build file does all the work, reinvoking Ant in many > > subdirectories and combining all the results. > > > > I've seen a lot of projects that require you to set environment variables > > and/or use a shell script wrapper. I don't get why. > > > > The only thing external to the Tapestry workspace is the directories for a > > couple of large, external tools: JBoss, FOP, Saxon and Clover. > > > > JBoss is needed because we build demos that plug into JBoss in a turnkey > > way. FOP is for DocBook to PDF. Saxon is for DocBook to HTML or DocBook > to > > Flow Objects (fed into FOP) ... I use Saxon because it is about 20x faster > > than Xalan doing the same job. Clover is proprietary source code coverage > > tool. > > > > Getting Ant to use Saxon instead of Xalan requires a few command line > > options that can be accomplished via the ANT_OPTS env variable: > > > > > ANT_OPTS=-Xmx256mb -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.cri > > > on.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=o > > rg.apache.crimson.jaxp.SAXParserFactoryImpl > > > > The other three external tools (JBoss, FOP and Clover) are identified in > the > > build.properties file which must be placed into the config directory. > This > > file sets three properties needed by the many Ant build scripts: > > > > jboss.dir > > fop.dir > > clover.dir > > > > Each of these is the absolute path to the respective tool. It is > important > > to use FORWARD SLASHES ONLY or you will get build errors. I've enclosed a > > copy that I use when I do builds. > > > > Clover has kindly donated a copy of their tool to Tapestry; a copy of > their > > distribution is in the support directory. > > > > The final piece of the puzzle is the disto build script. This is in the > > support directory. I typically copy this out to a temporary directory. I > > also copy my current build.properties file to the same directory. > > > > The distro build script has two targets. "setup" uses anonymous CVS to > grab > > a fresh copy of the Tapestry workspace. It uses export, so that the CVS > > directories are not exported. This takes about one minute. > > > > "build" copies the build.properties file into the exported workspace and > > invokes the "dist" target on the master build file. It then copies the > > resulting distro files back up to the current directory. This takes about > > nine minutes (on my new, blazing fast laptop, anyway). > > > > Side note: Tapestry has, checked into the repository, copies of DocBook > XML > > and the DocBook XSL distros. It automatically unpacks these as needed > > during the build. We may want to change things to make these addtiional, > > external tools as well. > > > > Side note: People have had compatibility issues when using Tapestry JARs > > compiled by the 1.4 compiler, even in 1.3 compatibility mode. I currently > > set my JAVA_HOME to a JDK 1.3 before doing the build to ensure maximum > > compatibility. > > > > Currently, three distro files are created: Tapestry-x.x-core.tar.gz is > the > > main distribution, containing the compiled JARs, external libraries (such > as > > OGNL and Log4J) and the source code (packaged into .jar files). > > > > Tapestry-x.x.-doc.tar.gz contains all the documentation for Tapestry; > > JavaDoc, Contributor's Guide, and the various manuals (in HTML and PDF). > > > > Tapestry-Web-x.x.tar.gz contains an image of the Tapestry web site, which > is > > similar to the doc distro, but includes the Clover code coverage report. > > > > Tapestry builds .tar.gz files currently because a) WinZip can open them > fine > > and b) they are smaller than the equivalent .zip files. > > > > I'm sure there'll be some impedance using Maven, but since Tapestry is > > already built to use straight Ant to perform full builds (albiet with a > > couple of configuration gotchas) I hope it will not be too tricky. > > > > ----- Original Message ----- > > From: <di...@mu...> > > To: "Andrew C. Oliver" <aco...@ap...> > > Cc: <tap...@li...>; > > <tap...@ja...> > > Sent: Monday, January 13, 2003 4:07 AM > > Subject: Re: [Tapestry-contrib] Getting back into it > > > > > > > tap...@li... wrote on 13/01/2003 > 09:07:03 > > > AM: > > > > I really recommend Mavenizing to this effect. I bet dion would help > > > > with that.. (http://jakarta.apache.org/maven) > > > > > > I'm happy to help with Mavenizing, if only for the docs part of the > > > process. We should also look and see if we can improve the docbook > plugin > > > for Maven (as it's rarely used and a little buggy!), to handle the > > > existing formats. > > > > > > > Alternatively (and this is what POI does) if maven doesn't do what you > > > > need Centipede (http://krysalis.org/centipede) and Forrest > > > > (http://xml.apache.org/forrest) might help. > > > > > > > > However it really depends on whether Maven works under gump... > > > Maven generates viable gump descriptors these days. > > > > > > > Gump should be one of our top priorities (jakarta.apache.org/gump) > > > > because it could do the builds and site publish for us... > > > +1 > > > -- > > > dIon Gillard, Multitask Consulting > > > Blog: http://www.freeroller.net/page/dion/Weblog > > > Work: http://www.multitask.com.au > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:tap...@ja...> > > > For additional commands, e-mail: > > <mailto:tap...@ja...> > > > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:tap...@ja...> > For additional commands, e-mail: <mailto:tap...@ja...> > |
|
From: Howard M. L. S. <hl...@at...> - 2003-01-13 12:48:26
|
I just want to caution against one thing: Please do not reoganize the source code directories yet. I know we want to organize the project structure more like an Apache project and that's fine ... but to do so now would cripple my ability to cleanly and safely merge in a huge number of changes from my branch and Mind Bridge is in the same boat with his branch. Once we put 2.3 to bed, we can merge in code changes into 2.4 and then we can rename packages and reorganize overall structure. ----- Original Message ----- From: "Howard M. Lewis Ship" <hl...@at...> To: "Tapestry development" <tap...@ja...> Cc: <tap...@li...>; <tap...@ja...> Sent: Monday, January 13, 2003 7:09 AM Subject: Re: [Tapestry-contrib] Getting back into it > To help with Maven, here's some notes about how releases are currently > built. Some of these notes overlap details in the Contributor's Guide, so > you should check that out as well. > > The master build file does all the work, reinvoking Ant in many > subdirectories and combining all the results. > > I've seen a lot of projects that require you to set environment variables > and/or use a shell script wrapper. I don't get why. > > The only thing external to the Tapestry workspace is the directories for a > couple of large, external tools: JBoss, FOP, Saxon and Clover. > > JBoss is needed because we build demos that plug into JBoss in a turnkey > way. FOP is for DocBook to PDF. Saxon is for DocBook to HTML or DocBook to > Flow Objects (fed into FOP) ... I use Saxon because it is about 20x faster > than Xalan doing the same job. Clover is proprietary source code coverage > tool. > > Getting Ant to use Saxon instead of Xalan requires a few command line > options that can be accomplished via the ANT_OPTS env variable: > > ANT_OPTS=-Xmx256mb -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.cri > son.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=o > rg.apache.crimson.jaxp.SAXParserFactoryImpl > > The other three external tools (JBoss, FOP and Clover) are identified in the > build.properties file which must be placed into the config directory. This > file sets three properties needed by the many Ant build scripts: > > jboss.dir > fop.dir > clover.dir > > Each of these is the absolute path to the respective tool. It is important > to use FORWARD SLASHES ONLY or you will get build errors. I've enclosed a > copy that I use when I do builds. > > Clover has kindly donated a copy of their tool to Tapestry; a copy of their > distribution is in the support directory. > > The final piece of the puzzle is the disto build script. This is in the > support directory. I typically copy this out to a temporary directory. I > also copy my current build.properties file to the same directory. > > The distro build script has two targets. "setup" uses anonymous CVS to grab > a fresh copy of the Tapestry workspace. It uses export, so that the CVS > directories are not exported. This takes about one minute. > > "build" copies the build.properties file into the exported workspace and > invokes the "dist" target on the master build file. It then copies the > resulting distro files back up to the current directory. This takes about > nine minutes (on my new, blazing fast laptop, anyway). > > Side note: Tapestry has, checked into the repository, copies of DocBook XML > and the DocBook XSL distros. It automatically unpacks these as needed > during the build. We may want to change things to make these addtiional, > external tools as well. > > Side note: People have had compatibility issues when using Tapestry JARs > compiled by the 1.4 compiler, even in 1.3 compatibility mode. I currently > set my JAVA_HOME to a JDK 1.3 before doing the build to ensure maximum > compatibility. > > Currently, three distro files are created: Tapestry-x.x-core.tar.gz is the > main distribution, containing the compiled JARs, external libraries (such as > OGNL and Log4J) and the source code (packaged into .jar files). > > Tapestry-x.x.-doc.tar.gz contains all the documentation for Tapestry; > JavaDoc, Contributor's Guide, and the various manuals (in HTML and PDF). > > Tapestry-Web-x.x.tar.gz contains an image of the Tapestry web site, which is > similar to the doc distro, but includes the Clover code coverage report. > > Tapestry builds .tar.gz files currently because a) WinZip can open them fine > and b) they are smaller than the equivalent .zip files. > > I'm sure there'll be some impedance using Maven, but since Tapestry is > already built to use straight Ant to perform full builds (albiet with a > couple of configuration gotchas) I hope it will not be too tricky. > > ----- Original Message ----- > From: <di...@mu...> > To: "Andrew C. Oliver" <aco...@ap...> > Cc: <tap...@li...>; > <tap...@ja...> > Sent: Monday, January 13, 2003 4:07 AM > Subject: Re: [Tapestry-contrib] Getting back into it > > > > tap...@li... wrote on 13/01/2003 09:07:03 > > AM: > > > I really recommend Mavenizing to this effect. I bet dion would help > > > with that.. (http://jakarta.apache.org/maven) > > > > I'm happy to help with Mavenizing, if only for the docs part of the > > process. We should also look and see if we can improve the docbook plugin > > for Maven (as it's rarely used and a little buggy!), to handle the > > existing formats. > > > > > Alternatively (and this is what POI does) if maven doesn't do what you > > > need Centipede (http://krysalis.org/centipede) and Forrest > > > (http://xml.apache.org/forrest) might help. > > > > > > However it really depends on whether Maven works under gump... > > Maven generates viable gump descriptors these days. > > > > > Gump should be one of our top priorities (jakarta.apache.org/gump) > > > because it could do the builds and site publish for us... > > +1 > > -- > > dIon Gillard, Multitask Consulting > > Blog: http://www.freeroller.net/page/dion/Weblog > > Work: http://www.multitask.com.au > > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:tap...@ja...> > > For additional commands, e-mail: > <mailto:tap...@ja...> > > > > > |
|
From: Howard M. L. S. <hl...@at...> - 2003-01-13 12:12:07
|
To help with Maven, here's some notes about how releases are currently built. Some of these notes overlap details in the Contributor's Guide, so you should check that out as well. The master build file does all the work, reinvoking Ant in many subdirectories and combining all the results. I've seen a lot of projects that require you to set environment variables and/or use a shell script wrapper. I don't get why. The only thing external to the Tapestry workspace is the directories for a couple of large, external tools: JBoss, FOP, Saxon and Clover. JBoss is needed because we build demos that plug into JBoss in a turnkey way. FOP is for DocBook to PDF. Saxon is for DocBook to HTML or DocBook to Flow Objects (fed into FOP) ... I use Saxon because it is about 20x faster than Xalan doing the same job. Clover is proprietary source code coverage tool. Getting Ant to use Saxon instead of Xalan requires a few command line options that can be accomplished via the ANT_OPTS env variable: ANT_OPTS=-Xmx256mb -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.cri mson.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=o rg.apache.crimson.jaxp.SAXParserFactoryImpl The other three external tools (JBoss, FOP and Clover) are identified in the build.properties file which must be placed into the config directory. This file sets three properties needed by the many Ant build scripts: jboss.dir fop.dir clover.dir Each of these is the absolute path to the respective tool. It is important to use FORWARD SLASHES ONLY or you will get build errors. I've enclosed a copy that I use when I do builds. Clover has kindly donated a copy of their tool to Tapestry; a copy of their distribution is in the support directory. The final piece of the puzzle is the disto build script. This is in the support directory. I typically copy this out to a temporary directory. I also copy my current build.properties file to the same directory. The distro build script has two targets. "setup" uses anonymous CVS to grab a fresh copy of the Tapestry workspace. It uses export, so that the CVS directories are not exported. This takes about one minute. "build" copies the build.properties file into the exported workspace and invokes the "dist" target on the master build file. It then copies the resulting distro files back up to the current directory. This takes about nine minutes (on my new, blazing fast laptop, anyway). Side note: Tapestry has, checked into the repository, copies of DocBook XML and the DocBook XSL distros. It automatically unpacks these as needed during the build. We may want to change things to make these addtiional, external tools as well. Side note: People have had compatibility issues when using Tapestry JARs compiled by the 1.4 compiler, even in 1.3 compatibility mode. I currently set my JAVA_HOME to a JDK 1.3 before doing the build to ensure maximum compatibility. Currently, three distro files are created: Tapestry-x.x-core.tar.gz is the main distribution, containing the compiled JARs, external libraries (such as OGNL and Log4J) and the source code (packaged into .jar files). Tapestry-x.x.-doc.tar.gz contains all the documentation for Tapestry; JavaDoc, Contributor's Guide, and the various manuals (in HTML and PDF). Tapestry-Web-x.x.tar.gz contains an image of the Tapestry web site, which is similar to the doc distro, but includes the Clover code coverage report. Tapestry builds .tar.gz files currently because a) WinZip can open them fine and b) they are smaller than the equivalent .zip files. I'm sure there'll be some impedance using Maven, but since Tapestry is already built to use straight Ant to perform full builds (albiet with a couple of configuration gotchas) I hope it will not be too tricky. ----- Original Message ----- From: <di...@mu...> To: "Andrew C. Oliver" <aco...@ap...> Cc: <tap...@li...>; <tap...@ja...> Sent: Monday, January 13, 2003 4:07 AM Subject: Re: [Tapestry-contrib] Getting back into it > tap...@li... wrote on 13/01/2003 09:07:03 > AM: > > I really recommend Mavenizing to this effect. I bet dion would help > > with that.. (http://jakarta.apache.org/maven) > > I'm happy to help with Mavenizing, if only for the docs part of the > process. We should also look and see if we can improve the docbook plugin > for Maven (as it's rarely used and a little buggy!), to handle the > existing formats. > > > Alternatively (and this is what POI does) if maven doesn't do what you > > need Centipede (http://krysalis.org/centipede) and Forrest > > (http://xml.apache.org/forrest) might help. > > > > However it really depends on whether Maven works under gump... > Maven generates viable gump descriptors these days. > > > Gump should be one of our top priorities (jakarta.apache.org/gump) > > because it could do the builds and site publish for us... > +1 > -- > dIon Gillard, Multitask Consulting > Blog: http://www.freeroller.net/page/dion/Weblog > Work: http://www.multitask.com.au > > > > > -- > To unsubscribe, e-mail: <mailto:tap...@ja...> > For additional commands, e-mail: <mailto:tap...@ja...> > > |
|
From: Malcolm E. <mal...@ho...> - 2003-01-12 23:50:53
|
Big +1 on the Marvenizing Tapestry. >From: "Andrew C. Oliver" <aco...@ap...> >To: "Howard M. Lewis Ship" <hl...@at...>, >tap...@li... >Subject: Re: [Tapestry-contrib] Getting back into it >Date: Sun, 12 Jan 2003 17:07:03 -0500 > >I really recommend Mavenizing to this effect. I bet dion would help with >that.. (http://jakarta.apache.org/maven) > >Alternatively (and this is what POI does) if maven doesn't do what you need >Centipede (http://krysalis.org/centipede) and Forrest >(http://xml.apache.org/forrest) might help. > >However it really depends on whether Maven works under gump... > >Gump should be one of our top priorities (jakarta.apache.org/gump) because >it could do the builds and site publish for us... > >-Andy > >Howard M. Lewis Ship wrote: >>Part of what you discuss may involve having multiple Tapestry modules. >>Not good or bad, just a statement. >> Yes, and we may need to reorganize things further to reflect the >>standard Apache project layout ... if we want to get the synnergy thing >>going, we want to make Tapestry "friendly" to other Apache developers. >> Renaming packages looks like a big delete-and-add to CVS, so that's a >>good time to also reorganize directory structure. We should brainstorm >>what that structure should look like. >> >> ----- Original Message ----- >> *From:* Geoff Longman <mailto:glo...@in...> >> *To:* Tapestry Contrib >><mailto:tap...@li...> >> *Cc:* tap...@ja... >> <mailto:tap...@ja...> >> *Sent:* Sunday, January 12, 2003 11:34 AM >> *Subject:* [Tapestry-contrib] Getting back into it >> >> Whoo-ee, I have to say that this past holiday season was the worst >> on record for me. >> Just before Christmas good friends of ours had a terrible accident >> and their little girl was quite badly burned. >> It'll be a tough road ahead for their family but everything is >> relatively ok now. >> Also, I had a bit of a health scare myself last week and on top >>of >> all that we have a baby due imminently. >> Note: having a baby ids a good thing, it just added to the overall >> stress this holiday season! >> So, forgive if I've been quite the last while. I'm easing back >>into >> the 'normal' things now... >> Glad to see that the Apache thing is rolling along. Kudos to >>Andy et al! >> Looking for something to do Tapestry-wise and I was wondering if >> anybody had any thoughts on >> the structure for the code base in CVS. >> Currently, everything is located under the top-level Tapestry >> folder. That incl the framework, vlib, clover, contrib, workbench, >> and the >> mock opera :-) that Howard has built for testing. >> Would it make sense, after the move, the package rename, the >>Gump >> build (don't really understand that) was done >> if we examined the structure and split some of it out to the top >>level? >> The current advantage is that one can check out 'Tapestry' and >>get >> everything at once. One disadvantage is that to examine, for >> example, the vlib using Spindle is quite difficult. >> As I said, I realize there's still a lot of work to do before >>making >> these kind of changes. But I'm willing to play around with this. >> Geoff >> Geoffrey Longman >> Intelligent Works Inc. >> >> > > > > > >------------------------------------------------------- >This SF.NET email is sponsored by: >SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! >http://www.vasoftware.com >_______________________________________________ >Tapestry-contrib mailing list >Tap...@li... >https://lists.sourceforge.net/lists/listinfo/tapestry-contrib _________________________________________________________________ MSN 8: advanced junk mail protection and 2 months FREE*. http://join.msn.com/?page=features/junkmail |
|
From: Andrew C. O. <aco...@ap...> - 2003-01-12 23:21:53
|
my bad its jakarta.apache.org/turbine/maven Andrew C. Oliver wrote: > I really recommend Mavenizing to this effect. I bet dion would help > with that.. (http://jakarta.apache.org/maven) > > Alternatively (and this is what POI does) if maven doesn't do what you > need Centipede (http://krysalis.org/centipede) and Forrest > (http://xml.apache.org/forrest) might help. > > However it really depends on whether Maven works under gump... > > Gump should be one of our top priorities (jakarta.apache.org/gump) > because it could do the builds and site publish for us... > > -Andy > > Howard M. Lewis Ship wrote: > >> Part of what you discuss may involve having multiple Tapestry >> modules. Not good or bad, just a statement. >> >> Yes, and we may need to reorganize things further to reflect the >> standard Apache project layout ... if we want to get the synnergy >> thing going, we want to make Tapestry "friendly" to other Apache >> developers. >> >> Renaming packages looks like a big delete-and-add to CVS, so that's a >> good time to also reorganize directory structure. We should >> brainstorm what that structure should look like. >> >> ----- Original Message ----- >> *From:* Geoff Longman <mailto:glo...@in...> >> *To:* Tapestry Contrib >> <mailto:tap...@li...> >> *Cc:* tap...@ja... >> <mailto:tap...@ja...> >> *Sent:* Sunday, January 12, 2003 11:34 AM >> *Subject:* [Tapestry-contrib] Getting back into it >> >> Whoo-ee, I have to say that this past holiday season was the worst >> on record for me. >> Just before Christmas good friends of ours had a terrible accident >> and their little girl was quite badly burned. >> It'll be a tough road ahead for their family but everything is >> relatively ok now. >> Also, I had a bit of a health scare myself last week and on >> top of >> all that we have a baby due imminently. >> Note: having a baby ids a good thing, it just added to the overall >> stress this holiday season! >> So, forgive if I've been quite the last while. I'm easing >> back into >> the 'normal' things now... >> Glad to see that the Apache thing is rolling along. Kudos to >> Andy et al! >> Looking for something to do Tapestry-wise and I was wondering if >> anybody had any thoughts on >> the structure for the code base in CVS. >> Currently, everything is located under the top-level Tapestry >> folder. That incl the framework, vlib, clover, contrib, workbench, >> and the >> mock opera :-) that Howard has built for testing. >> Would it make sense, after the move, the package rename, the >> Gump >> build (don't really understand that) was done >> if we examined the structure and split some of it out to the top >> level? >> The current advantage is that one can check out 'Tapestry' >> and get >> everything at once. One disadvantage is that to examine, for >> example, the vlib using Spindle is quite difficult. >> As I said, I realize there's still a lot of work to do before >> making >> these kind of changes. But I'm willing to play around with this. >> Geoff >> Geoffrey Longman >> Intelligent Works Inc. >> > > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Tapestry-contrib mailing list > Tap...@li... > https://lists.sourceforge.net/lists/listinfo/tapestry-contrib > |
|
From: Andrew C. O. <aco...@ap...> - 2003-01-12 22:08:30
|
I really recommend Mavenizing to this effect. I bet dion would help with that.. (http://jakarta.apache.org/maven) Alternatively (and this is what POI does) if maven doesn't do what you need Centipede (http://krysalis.org/centipede) and Forrest (http://xml.apache.org/forrest) might help. However it really depends on whether Maven works under gump... Gump should be one of our top priorities (jakarta.apache.org/gump) because it could do the builds and site publish for us... -Andy Howard M. Lewis Ship wrote: > Part of what you discuss may involve having multiple Tapestry modules. > Not good or bad, just a statement. > > Yes, and we may need to reorganize things further to reflect the > standard Apache project layout ... if we want to get the synnergy thing > going, we want to make Tapestry "friendly" to other Apache developers. > > Renaming packages looks like a big delete-and-add to CVS, so that's a > good time to also reorganize directory structure. We should brainstorm > what that structure should look like. > > ----- Original Message ----- > *From:* Geoff Longman <mailto:glo...@in...> > *To:* Tapestry Contrib <mailto:tap...@li...> > *Cc:* tap...@ja... > <mailto:tap...@ja...> > *Sent:* Sunday, January 12, 2003 11:34 AM > *Subject:* [Tapestry-contrib] Getting back into it > > Whoo-ee, I have to say that this past holiday season was the worst > on record for me. > Just before Christmas good friends of ours had a terrible accident > and their little girl was quite badly burned. > It'll be a tough road ahead for their family but everything is > relatively ok now. > > Also, I had a bit of a health scare myself last week and on top of > all that we have a baby due imminently. > Note: having a baby ids a good thing, it just added to the overall > stress this holiday season! > > So, forgive if I've been quite the last while. I'm easing back into > the 'normal' things now... > > Glad to see that the Apache thing is rolling along. Kudos to Andy et al! > > Looking for something to do Tapestry-wise and I was wondering if > anybody had any thoughts on > the structure for the code base in CVS. > > Currently, everything is located under the top-level Tapestry > folder. That incl the framework, vlib, clover, contrib, workbench, > and the > mock opera :-) that Howard has built for testing. > > Would it make sense, after the move, the package rename, the Gump > build (don't really understand that) was done > if we examined the structure and split some of it out to the top level? > > The current advantage is that one can check out 'Tapestry' and get > everything at once. One disadvantage is that to examine, for > example, the vlib using Spindle is quite difficult. > > As I said, I realize there's still a lot of work to do before making > these kind of changes. But I'm willing to play around with this. > > Geoff > > Geoffrey Longman > Intelligent Works Inc. > > > |
|
From: Geoff L. <glo...@in...> - 2003-01-12 16:55:57
|
Yeah, the module idea works too. Although, I dunno how it would work in =
the Vlib case specifically as there are three folders at the same level, =
Vlib, VlibBeans, and VlibEAR.
I will browse around some jakarta projects to see how they have laid =
things out. Will post findings to the wiki.
Geoff
----- Original Message -----=20
From: Howard M. Lewis Ship=20
To: Geoff Longman ; Tapestry Contrib=20
Cc: tap...@ja...=20
Sent: Sunday, January 12, 2003 11:46 AM
Subject: Re: [Tapestry-contrib] Getting back into it
Part of what you discuss may involve having multiple Tapestry modules. =
Not good or bad, just a statement.
Yes, and we may need to reorganize things further to reflect the =
standard Apache project layout ... if we want to get the synnergy thing =
going, we want to make Tapestry "friendly" to other Apache developers.
Renaming packages looks like a big delete-and-add to CVS, so that's a =
good time to also reorganize directory structure. We should brainstorm =
what that structure should look like.
----- Original Message -----=20
From: Geoff Longman=20
To: Tapestry Contrib=20
Cc: tap...@ja...=20
Sent: Sunday, January 12, 2003 11:34 AM
Subject: [Tapestry-contrib] Getting back into it
Whoo-ee, I have to say that this past holiday season was the worst =
on record for me.
Just before Christmas good friends of ours had a terrible accident =
and their little girl was quite badly burned.=20
It'll be a tough road ahead for their family but everything is =
relatively ok now.
Also, I had a bit of a health scare myself last week and on top of =
all that we have a baby due imminently.
Note: having a baby ids a good thing, it just added to the overall =
stress this holiday season!
So, forgive if I've been quite the last while. I'm easing back into =
the 'normal' things now...
Glad to see that the Apache thing is rolling along. Kudos to Andy et =
al!
Looking for something to do Tapestry-wise and I was wondering if =
anybody had any thoughts on
the structure for the code base in CVS.
Currently, everything is located under the top-level Tapestry =
folder. That incl the framework, vlib, clover, contrib, workbench, and =
the=20
mock opera :-) that Howard has built for testing.
Would it make sense, after the move, the package rename, the Gump =
build (don't really understand that) was done
if we examined the structure and split some of it out to the top =
level?
The current advantage is that one can check out 'Tapestry' and get =
everything at once. One disadvantage is that to examine, for example, =
the vlib using Spindle is quite difficult.
As I said, I realize there's still a lot of work to do before making =
these kind of changes. But I'm willing to play around with this.
Geoff
Geoffrey Longman
Intelligent Works Inc.
|
2 messages has been excluded from this view by a project administrator.
