You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(4) |
Feb
(10) |
Mar
|
Apr
(4) |
May
|
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2003 |
Jan
(1) |
Feb
(1) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mehmet B. <me...@bi...> - 2003-03-03 10:26:51
|
no, i'm not using jikes, but just that you know, the problem went away when i switched back to jdk 1.3.1. of course, now, my tomcat doesn't run anymore (because i have the jdk 1.4 version installed), but i haven't had time yet to delve into it deeper. for the moment, i keep switching the jdk, depending on what i'm doing. probably, with time, it will fix itself :-) > -----Original Message----- > From: che...@li... > [mailto:che...@li...]On Behalf Of Sébastien > Koechlin > Sent: Saturday, March 01, 2003 16:23 > To: che...@li... > Subject: Re: [Chello-users] Can't compile Chello > > > > I have just checked out chello from CVS and am trying to build it, but I > > get the following error message: > > > > error: Invalid class file format in > > c:\j2sdk1.4.1_01\jre\lib\rt.jar(java/util/Date.class). The major.minor > > version '48.0' is too recent for this tool to understand. > > > > A Google search turned out some mumblings about copying "tools.jar" from > > JAVA_HOME to the Tomcat Directory, but that did'nt help, and I can find > > no tools.jar in chello, just jmxtools.jar. > > Are you using jikes ? This error is probably not related to chello nor > cocoon, but probably because your compilator does not work with classes > from your java virtual machine (rt.jr => RunTime standard classes) > > -- > Sébastien Koechlin - iVision > Tél : +33 (0)1 40 07 13 33 > Fax : +33 (0)1 40 17 90 30 > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Chello-users mailing list > Che...@li... > https://lists.sourceforge.net/lists/listinfo/chello-users > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.459 / Virus Database: 258 - Release Date: 25.02.2003 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.459 / Virus Database: 258 - Release Date: 25.02.2003 |
From: Sébastien K. <sko...@iv...> - 2003-03-01 15:22:43
|
> I have just checked out chello from CVS and am trying to build it, but I > get the following error message: > > error: Invalid class file format in > c:\j2sdk1.4.1_01\jre\lib\rt.jar(java/util/Date.class). The major.minor > version '48.0' is too recent for this tool to understand. > > A Google search turned out some mumblings about copying "tools.jar" from > JAVA_HOME to the Tomcat Directory, but that did'nt help, and I can find > no tools.jar in chello, just jmxtools.jar. Are you using jikes ? This error is probably not related to chello nor cocoon, but probably because your compilator does not work with classes from your java virtual machine (rt.jr => RunTime standard classes) -- Sébastien Koechlin - iVision Tél : +33 (0)1 40 07 13 33 Fax : +33 (0)1 40 17 90 30 |
From: Mehmet B. <me...@bi...> - 2003-02-17 15:37:35
|
Hi all, I have just checked out chello from CVS and am trying to build it, but I get the following error message: error: Invalid class file format in c:\j2sdk1.4.1_01\jre\lib\rt.jar(java/util/Date.class). The major.minor version '48.0' is too recent for this tool to understand. A Google search turned out some mumblings about copying "tools.jar" from JAVA_HOME to the Tomcat Directory, but that did'nt help, and I can find no tools.jar in chello, just jmxtools.jar. I am using, win2k, java 1.4.1_01, tomcat 4.0.4 and CVS-HEAD of chello. Any suggestions? Cheers, Memo --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 27.01.2003 |
From: <jm...@ib...> - 2003-01-08 21:59:56
|
hello, im new to the list. ive been looking for xsldoc.org to check = out some documentation. does anyone know where they disappeared to? - j. -------------------------- Jay Myers Se=F1or Programmer=20 jm...@ib... |
From: thats r. <tha...@ho...> - 2002-10-11 13:17:06
|
Your Email Client does not support MIME encoding. Please upgrade to MIME-enabled Email Client (almost every modern Email Client is MIME-capable). |
From: David C. <da...@ne...> - 2002-07-04 18:55:42
|
The sitemap.xmap.cocoon-2rc2 is the full sitemap.xmap that comes with cocoon when you download the full version from xml.apache.org/cocoon. It has everything in it, including the kitchen sink and instructions on how to change the washers. The sitemap.xmap serves the same purpose but has the settings customized for the Chello demo app. If you diff the two files it's easy to see why they cut a lot of the stuff... it's mostly <map> information for the demos and documentation that comes with cocoon. Dave |
From: icewind <ice...@ya...> - 2002-07-01 16:50:28
|
What is the purpose of the sitemap.xmap.xocoon-2rc2 file in the web directory of the chello application? Is there any relation to the sitemap.xmap file? Thanks. __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: Bruce K. <bru...@me...> - 2002-06-03 15:23:51
|
http://localhost:8080/chello/ The build should have created a chello sub-directory in your Tomcat = webapps directory. HTH, Bruce >>> Margrit John <mar...@sw...> 06/03/02 09:59AM >>> Hi! I made an installation of chello. It seems to work, tomcat is working = and=20 finally also ./build.sh .=20 Now my question: Where do I have to point my browser to? I get the tomcat page at:=20 http://127.0.0.1:8080=20 According to the sitemap, I should be able to add "/welcome" and see = the=20 Welcome Page. This doesn't work. Do I miss something here? Thanks=20 Margrit _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm=20 _______________________________________________ Chello-users mailing list Che...@li...=20 https://lists.sourceforge.net/lists/listinfo/chello-users |
From: Margrit J. <mar...@sw...> - 2002-06-03 14:53:07
|
Hi! I made an installation of chello. It seems to work, tomcat is working and= =20 finally also ./build.sh .=20 Now my question: Where do I have to point my browser to? I get the tomcat page at:=20 http://127.0.0.1:8080 According to the sitemap, I should be able to add "/welcome" and see the=20 Welcome Page. This doesn't work. Do I miss something here? Thanks=20 Margrit |
From: Bruce K. <bru...@me...> - 2002-04-24 13:26:03
|
Hello again, Cyril, I did not intend in any way to criticize the great work you have = done on chello. I'm sure I speak for all chello users when I say how = appreciative we are that you and your company have donated this work to = the open source community. Maybe my point should have been directed to = the Cocoon developers. I think if chello, or a project like it, was an = integral part of the Cocoon build then the maintenance would pretty much = take care of itself. Have there ever been any discussions along these = lines? Kindest regards, Bruce >>> cca...@ya... 04/24/02 03:01AM >>> We made chello in our company because we developped several Cocoon applications and we decided to publish this work. Chello is NOT unsupported and unmaintened, but people at iVision will improve it, only if 1 - a new project requires it, and we will have new cocoon project 2 - on our spare time, but we do not have any spare time As Bruce wrote : "Keeping Chello in step with Cocoon seems like it is going to be an onerous task" As Phil noticed, here's no long term plans for Chello as it depends on future projects starting from it. HOWEVER, Chello is NOT the iVision's thing and ANYBODY can participate in the project. Register at Sourceforge and send a request to cca...@iv... and you can join the team |
From: <cca...@ya...> - 2002-04-24 08:01:33
|
We made chello in our company because we developped several Cocoon applications and we decided to publish this work. Chello is NOT unsupported and unmaintened, but people at iVision will improve it, only if 1 - a new project requires it, and we will have new cocoon project 2 - on our spare time, but we do not have any spare time As Bruce wrote : "Keeping Chello in step with Cocoon seems like it is going to be an onerous task" As Phil noticed, here's no long term plans for Chello as it depends on future projects starting from it. HOWEVER, Chello is NOT the iVision's thing and ANYBODY can participate in the project. Register at Sourceforge and send a request to cca...@iv... and you can join the team --- Bruce Krautbauer <bru...@me...> a écrit : > Hi all, I got Chello to build and run on Cocoon > 2.1-dev with Tomcat 4.0.4b2 and JDK 1.4.0 on Win2K > using the following procedure: > > 0. Assuming JDK 1.4.0, Tomcat 4.0.4b2 and Cocoon > 2.1-dev installed and working. Simply following the > instructions seems to work. > 1. CVS checkout of chello. > 2. Minor edit to build.bat to remove quotes from > around %TOMCAT_HOME% on line 14. (Probably should > remove quotes from around %JAVA_HOME% on line 9 and > %ANT_HOME% on line 19 also.) > 3. Updated the .jars in chello\lib from > xml-cocoon2\lib\core and xml-cocoon2\lib\optional. > I did this the lazy way by simply copying all the > .jars from the two Cocoon directories to the chello > directory and then deleting the 'old' versions. I > know this leaves .jars there that aren't needed, but > I'm not smart enough to know which ones to remove. > 4. Copied > xml-cocoon2\build\cocoon\webapp\WEB-INF\lib\cocoon-2.1-dev.jar > to chello\lib, removed cocoon-2.0.2rc2.jar. > 5. Copied > xml-cocoon2\build\cocoon\webapp\WEB-INF\cocoon.xconf > to chello\etc and edited it to remove all of the > contents of the <datasources> section and commented > out the <hsqldb-server> section. > 5a. Deleted chello\web\cocoon.xconf > 6. Copied > xml-cocoon2\build\cocoon\webapp\WEB-INF\web.xml to > chello\etc and edited it to change the > <display-name> and <description> sections. > 7. Copied > xml-cocoon2\build\cocoon\webapp\WEB-INF\logkit.xconf > to chello\etc. > 8. Created a new chello\web\sitemap.xmap by starting > with a copy of > xml-cocoon2\build\cocoon\webapp\sitemap.xmap. I > deleted all of the map:actions, map:resources, > map:action-sets, and replaced the pipelines section > with the pipelines section from the existing chello > sitemap. > 9. Edited chello\web\docs\hello.xsp to remove the > database example. > 10. Edited chello\build.xml to reflect new location > of cocoon.xconf by adding the following line after > <mkdir dir="${deploy.home}/WEB-INF"/> > <copy file="etc/cocoon.xconf" > tofile="${deploy.home}/WEB-INF/cocoon.xconf"/> > > This version builds and tests OK. Being new to this > there may be other changes that should be made that > I am not aware of. > > <editorial> > Chello is an invaluable concept, especially for > something like Cocoon, which really isn't anything > without applications. Keeping Chello in step with > Cocoon seems like it is going to be an onerous task. > The alternative, starting with the Cocoon sample > and deleting stuff, isn't very appealing either, > plus you don't get the benefit of the 'complete' > build process Chello gives you. I think the best > approach would be to have Chello moved into the > Cocoon project and maintained as an integral part of > it. > </editorial> > > Bruce > > > > _______________________________________________ > Chello-users mailing list > Che...@li... > https://lists.sourceforge.net/lists/listinfo/chello-users > > > ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com |
From: Phil B. <ph...@tc...> - 2002-04-15 22:39:49
|
Hi Bruce, Thanks for the update information. Chello is a great idea, but no one seems to have the time to maintain or support it. I don't know what the long term plan is for chello. Thanks for your time with this project. Phil On Tuesday, April 16, 2002, at 01:51 AM, Bruce Krautbauer wrote: > Hi all, I got Chello to build and run on Cocoon 2.1-dev with Tomcat > 4.0.4b2 and JDK 1.4.0 on Win2K using the following procedure: > > 0. Assuming JDK 1.4.0, Tomcat 4.0.4b2 and Cocoon 2.1-dev installed and > working. Simply following the instructions seems to work. > 1. CVS checkout of chello. > 2. Minor edit to build.bat to remove quotes from around %TOMCAT_HOME% > on line 14. (Probably should remove quotes from around %JAVA_HOME% on > line 9 and %ANT_HOME% on line 19 also.) > 3. Updated the .jars in chello\lib from xml-cocoon2\lib\core and > xml-cocoon2\lib\optional. I did this the lazy way by simply copying > all the .jars from the two Cocoon directories to the chello directory > and then deleting the 'old' versions. I know this leaves .jars there > that aren't needed, but I'm not smart enough to know which ones to > remove. > 4. Copied xml-cocoon2\build\cocoon\webapp\WEB- > INF\lib\cocoon-2.1-dev.jar to chello\lib, removed cocoon-2.0.2rc2.jar. > 5. Copied xml-cocoon2\build\cocoon\webapp\WEB-INF\cocoon.xconf to > chello\etc and edited it to remove all of the contents of the > <datasources> section and commented out the <hsqldb-server> section. > 5a. Deleted chello\web\cocoon.xconf > 6. Copied xml-cocoon2\build\cocoon\webapp\WEB-INF\web.xml to chello\etc > and edited it to change the <display-name> and <description> sections. > 7. Copied xml-cocoon2\build\cocoon\webapp\WEB-INF\logkit.xconf to > chello\etc. > 8. Created a new chello\web\sitemap.xmap by starting with a copy of > xml-cocoon2\build\cocoon\webapp\sitemap.xmap. I deleted all of the > map:actions, map:resources, map:action-sets, and replaced the pipelines > section with the pipelines section from the existing chello sitemap. > 9. Edited chello\web\docs\hello.xsp to remove the database example. > 10. Edited chello\build.xml to reflect new location of cocoon.xconf by > adding the following line after <mkdir dir="${deploy.home}/WEB-INF"/> > <copy file="etc/cocoon.xconf" tofile="${deploy.home}/WEB- > INF/cocoon.xconf"/> > > This version builds and tests OK. Being new to this there may be other > changes that should be made that I am not aware of. > > <editorial> > Chello is an invaluable concept, especially for something like Cocoon, > which really isn't anything without applications. Keeping Chello in > step with Cocoon seems like it is going to be an onerous task. The > alternative, starting with the Cocoon sample and deleting stuff, isn't > very appealing either, plus you don't get the benefit of the 'complete' > build process Chello gives you. I think the best approach would be to > have Chello moved into the Cocoon project and maintained as an integral > part of it. > </editorial> > > Bruce > > > > _______________________________________________ > Chello-users mailing list > Che...@li... > https://lists.sourceforge.net/lists/listinfo/chello-users > |
From: Bruce K. <bru...@me...> - 2002-04-15 15:52:09
|
Hi all, I got Chello to build and run on Cocoon 2.1-dev with Tomcat = 4.0.4b2 and JDK 1.4.0 on Win2K using the following procedure: 0. Assuming JDK 1.4.0, Tomcat 4.0.4b2 and Cocoon 2.1-dev installed and = working. Simply following the instructions seems to work. 1. CVS checkout of chello. 2. Minor edit to build.bat to remove quotes from around %TOMCAT_HOME% on = line 14. (Probably should remove quotes from around %JAVA_HOME% on line 9 = and %ANT_HOME% on line 19 also.) 3. Updated the .jars in chello\lib from xml-cocoon2\lib\core and xml-cocoon= 2\lib\optional. I did this the lazy way by simply copying all the .jars = from the two Cocoon directories to the chello directory and then deleting = the 'old' versions. I know this leaves .jars there that aren't needed, = but I'm not smart enough to know which ones to remove. 4. Copied xml-cocoon2\build\cocoon\webapp\WEB-INF\lib\cocoon-2.1-dev.jar = to chello\lib, removed cocoon-2.0.2rc2.jar. 5. Copied xml-cocoon2\build\cocoon\webapp\WEB-INF\cocoon.xconf to = chello\etc and edited it to remove all of the contents of the <datasources>= section and commented out the <hsqldb-server> section. 5a. Deleted chello\web\cocoon.xconf 6. Copied xml-cocoon2\build\cocoon\webapp\WEB-INF\web.xml to chello\etc = and edited it to change the <display-name> and <description> sections. 7. Copied xml-cocoon2\build\cocoon\webapp\WEB-INF\logkit.xconf to = chello\etc. 8. Created a new chello\web\sitemap.xmap by starting with a copy of = xml-cocoon2\build\cocoon\webapp\sitemap.xmap. I deleted all of the = map:actions, map:resources, map:action-sets, and replaced the pipelines = section with the pipelines section from the existing chello sitemap. 9. Edited chello\web\docs\hello.xsp to remove the database example. 10. Edited chello\build.xml to reflect new location of cocoon.xconf by = adding the following line after <mkdir dir=3D"${deploy.home}/WEB-INF"/> <copy file=3D"etc/cocoon.xconf" tofile=3D"${deploy.home}/WEB-INF/cocoo= n.xconf"/> This version builds and tests OK. Being new to this there may be other = changes that should be made that I am not aware of. <editorial> Chello is an invaluable concept, especially for something like Cocoon, = which really isn't anything without applications. Keeping Chello in step = with Cocoon seems like it is going to be an onerous task. The alternative,= starting with the Cocoon sample and deleting stuff, isn't very appealing = either, plus you don't get the benefit of the 'complete' build process = Chello gives you. I think the best approach would be to have Chello moved = into the Cocoon project and maintained as an integral part of it. </editorial> Bruce |
From: von S. T. (G. FPI)
<Tho...@gx...> - 2002-02-08 15:40:29
|
I just discovered that I sent that whole thing in HTML...*very* sorry about that, I'm stuck with Outlook here at work and I'm not used to dealing with it.... So, here it is again, in text this time (I think). ============================================================================ ==== [ Note: I may be *totally* missing the point of what CHello is.....I'm new to Cocoon and CHello alike. ] <as I understand it> Given that CHello is meant as the "Hello World" for Cocoon, it could logically be converted into a very useful resource of tutorials and examples introducing various aspects of Cocoon processing/usage techniques. </as I understand it> The Apache sites generally provide enough information to install the software and get it up and running, but beyond that they provide little more than links for further information gathering. This is fine with me (and IMHO, the way it should stay), but having a central repository of HOWTO's and related information for Cocoon would be an excellent resource to have, and I think CHello is currently already pointing in that direction....it just needs to start moving that way. Is there already a central site for cocoon related information? I'm thinking of something along the lines of vim online (http://vim.sf.net) except geared more towards introductory information....although, I would see no reason to turn away "veteran tips"..... At any rate, upon first finding/visiting chello I got the impression that the site was just begging to go in that kind of direction...and seeing as how there doesn't seem to be anything else of the sort around (yet), well, why not do it? Granted, the amount of work involved in getting something like that together isn't minimal, but once you make your intentions known to the cocoon-users list (and whatever other resources you can think of) you might be able to get enough volunteers and contributors to make the individual workloads reasonable.....or just go under the lovely Open Sourced principal of "it'll be done when its done"... So, that's my bit for today.... waddaya think? - The overly enthusiastic rookie, Tom. > -----Original Message----- > From: Cyril Cambien [mailto:cca...@iv...] > Sent: Friday, February 08, 2002 9:51 AM > To: Phil Blake > Cc: che...@li... > Subject: Re: [Chello-users] Authentication > > > We'd like to keep Chello as general as possible. This is > difficult to define > if an given functionality is "general" or not. More, a > component can be > reusable, interesting for many persons, but not "general". (like an > authentication manager for Gemstone, for instance (-; ) > So i think specific stuff should not be part of the standard > distribution. > Nevertheless, I think we can host it as sub-projects under the Chello > project. > > -- Cyril > > Phil Blake wrote: > > > Just as a matter of interest, is there anyone else lurking > on this list? > > > > I am writing an authentication manager that uses GemStone Object > > Database as it's storage. This is the kind of thing that > you only ever > > do once with each server environment. > > > > Although I don't expect that there are that many people > using GemStone > > and cocoon, I believe these kinds of tools should be > collected and made > > available to the chello project. I would like to see chello > be not only > > a great base for starting any cocoon project, but an > excellent set of > > resources that provide solutions to common problems. > > > > That is all. > > > > Any comments or ideas? > > > > Thanks. Have fun, > > > > Phil > > > > _______________________________________________ > > Chello-users mailing list > > Che...@li... > > https://lists.sourceforge.net/lists/listinfo/chello-users > > > _______________________________________________ > Chello-users mailing list > Che...@li... > https://lists.sourceforge.net/lists/listinfo/chello-users > |
From: von S. T. (G. FPI)
<Tho...@gx...> - 2002-02-08 15:36:52
|
[ Note: I may be *totally* missing the point of what CHello is.....I'm new to Cocoon and CHello alike. ] <as I understand it> Given that CHello is meant as the "Hello World" for Cocoon, it could logically be converted into a very useful resource of tutorials and examples introducing various aspects of Cocoon processing/usage techniques. </as I understand it> The Apache sites generally provide enough information to install the software and get it up and running, but beyond that they provide little more than links for further information gathering. This is fine with me (and IMHO, the way it should stay), but having a central repository of HOWTO's and related information for Cocoon would be an excellent resource to have, and I think CHello is currently already pointing in that direction....it just needs to start moving that way. Is there already a central site for cocoon related information? I'm thinking of something along the lines of vim online (http://vim.sf.net) except geared more towards introductory information....although, I would see no reason to turn away "veteran tips"..... At any rate, upon first finding/visiting chello I got the impression that the site was just begging to go in that kind of direction...and seeing as how there doesn't seem to be anything else of the sort around (yet), well, why not do it? Granted, the amount of work involved in getting something like that together isn't minimal, but once you make your intentions known to the cocoon-users list (and whatever other resources you can think of) you might be able to get enough volunteers and contributors to make the individual workloads reasonable.....or just go under the lovely Open Sourced principal of "it'll be done when its done"... So, that's my bit for today.... waddaya think? - The overly enthusiastic rookie, Tom. > -----Original Message----- > From: Cyril Cambien [mailto:cca...@iv...] > Sent: Friday, February 08, 2002 9:51 AM > To: Phil Blake > Cc: che...@li... > Subject: Re: [Chello-users] Authentication > > > We'd like to keep Chello as general as possible. This is > difficult to define > if an given functionality is "general" or not. More, a > component can be > reusable, interesting for many persons, but not "general". (like an > authentication manager for Gemstone, for instance (-; ) > So i think specific stuff should not be part of the standard > distribution. > Nevertheless, I think we can host it as sub-projects under the Chello > project. > > -- Cyril > > Phil Blake wrote: > > > Just as a matter of interest, is there anyone else lurking > on this list? > > > > I am writing an authentication manager that uses GemStone Object > > Database as it's storage. This is the kind of thing that > you only ever > > do once with each server environment. > > > > Although I don't expect that there are that many people > using GemStone > > and cocoon, I believe these kinds of tools should be > collected and made > > available to the chello project. I would like to see chello > be not only > > a great base for starting any cocoon project, but an > excellent set of > > resources that provide solutions to common problems. > > > > That is all. > > > > Any comments or ideas? > > > > Thanks. Have fun, > > > > Phil > > > > _______________________________________________ > > Chello-users mailing list > > Che...@li... > > https://lists.sourceforge.net/lists/listinfo/chello-users > > > _______________________________________________ > Chello-users mailing list > Che...@li... > https://lists.sourceforge.net/lists/listinfo/chello-users > |
From: Cyril C. <cca...@iv...> - 2002-02-08 14:43:12
|
We'd like to keep Chello as general as possible. This is difficult to define if an given functionality is "general" or not. More, a component can be reusable, interesting for many persons, but not "general". (like an authentication manager for Gemstone, for instance (-; ) So i think specific stuff should not be part of the standard distribution. Nevertheless, I think we can host it as sub-projects under the Chello project. -- Cyril Phil Blake wrote: > Just as a matter of interest, is there anyone else lurking on this list? > > I am writing an authentication manager that uses GemStone Object > Database as it's storage. This is the kind of thing that you only ever > do once with each server environment. > > Although I don't expect that there are that many people using GemStone > and cocoon, I believe these kinds of tools should be collected and made > available to the chello project. I would like to see chello be not only > a great base for starting any cocoon project, but an excellent set of > resources that provide solutions to common problems. > > That is all. > > Any comments or ideas? > > Thanks. Have fun, > > Phil > > _______________________________________________ > Chello-users mailing list > Che...@li... > https://lists.sourceforge.net/lists/listinfo/chello-users |
From: Cyril C. <cca...@iv...> - 2002-02-08 13:33:38
|
1/ concerning the "Getting Started", you can find a QUICKSTART file in the standard distribution. However, this file can surely be improved and any help is welcome 2/ Yes, Chello works with many web container, including Tomcat 4, Weblogic and many. For the moment, our "reference" container is Tomcat 3, but I think we should move to Tomcat 4 as it seems to be fairly stable now 3/ Concerning ANT, you're right. Our goal is to have a stand-alone environment except for Tomcat and the JDK. This is why Chello includes Ant. If we continue to do so, I agree Chello should not use ANT_HOME. Regards, -- Cyril Henrik J=F8rgensen wrote: > Hi > > First of all - I think you are doing a nice job here! We need some > structure on the development process =85.. > > I=92ve installed chello for the first time yesterday. I managed to buil= d > and access http://localhost/chello (fairly easy :-)) but I have some > comments. > > Install: > > Write something that says =93unzip the xxx.zip into a directory of your > choice=94 =96 for the newcomer this would be a great help. Maybe this > could be covert by a =93Getting started=94 guide but then again time, > time timeJ and you already have a lot of the information on your site. > > Install/Tomcat section: > > =93requires Tomcat 3.0=94, correct this to =93Tomcat 3.0+=94 . I had no > problems with Tomcat 4.0 and if chello is build on the Cocoon 2 > framework it should be valid to say. > > Compiling: > > An entry is missing for win32 in the clean section like > > [unix] ./build.sh clean > > [win32] build clean > > [Error] The build.bat command for win32 is not working properly if you > already have Ant installed and declared ANT_HOME =96 the classpath > points to some jar files only present in the ant directory of your > distribution. > > I know my comments aren=92t critical for the project but I hope you can > use it. > > Sincerely > > HenrikJ=F8rgensen > |
From: Cyril C. <cca...@iv...> - 2002-02-08 13:24:51
|
S=E9bastien Koechlin (sk...@iv...) Cyril Cambien (cy...@iv...) By the way, we will be happy to get some help, both for keeping Chello up to date and for improving it. -- Cyril Phil Blake wrote: > Hi all (if there is an all), > > Who is working on keeping chello up to date? > > Thanks, > > Phil > > _______________________________________________ > Chello-users mailing list > Che...@li... > https://lists.sourceforge.net/lists/listinfo/chello-users |
From: von S. T. (G. FPI)
<Tho...@gx...> - 2002-02-06 13:18:56
|
heh, as far as I have seen, YOU are the only^H^H^H^Hbest candidate for the job. :-) -Tom > -----Original Message----- > From: Phil Blake [mailto:ph...@tc...] > Sent: Tuesday, February 05, 2002 10:46 PM > To: che...@li... > Subject: [Chello-users] Keeping chello up to date > > > Hi all (if there is an all), > > Who is working on keeping chello up to date? > > Thanks, > > Phil > > > _______________________________________________ > Chello-users mailing list > Che...@li... > https://lists.sourceforge.net/lists/listinfo/chello-users > |
From: Phil B. <ph...@tc...> - 2002-02-06 03:46:43
|
Hi all (if there is an all), Who is working on keeping chello up to date? Thanks, Phil |
From: Phil B. <ph...@tc...> - 2002-02-05 22:25:09
|
Just as a matter of interest, is there anyone else lurking on this list? I am writing an authentication manager that uses GemStone Object Database as it's storage. This is the kind of thing that you only ever do once with each server environment. Although I don't expect that there are that many people using GemStone and cocoon, I believe these kinds of tools should be collected and made available to the chello project. I would like to see chello be not only a great base for starting any cocoon project, but an excellent set of resources that provide solutions to common problems. That is all. Any comments or ideas? Thanks. Have fun, Phil |
From: Phil B. <ph...@tc...> - 2002-02-05 22:21:04
|
> From: Phil Blake <ph...@tc...> > Date: Wed Feb 06, 2002 09:19:33 AM Australia/Sydney > To: "von Schwerdtner, Thomas (GXS, FPI)"=20 > <Tho...@gx...> > Subject: Re: [Chello-users] Intro questions > > Hiya, > > I'm not the person to be answering this but I assume this list is to=20= > help those of us who are working with the chello 'development kit' for=20= > want of a better phrase. > > Because it is a combination of many other bits of software, this list=20= > will deal with them working together, and enhancing the chello base=20 > application. > > I'm guessing that questions relating to individual components of = chello=20 > would be better answered by their mailing lists as the majority of=20 > their users will be there. > > I don't know if there is anyone here apart from you and I. :) > > Have fun, > > Phil > > > On Wednesday, February 6, 2002, at 03:34 AM, von Schwerdtner, Thomas=20= > (GXS, FPI) wrote: > >> Hello, >> >> =A0=A0 Is this list meant to serve as a sort of "cocoon-users-newbie" = list? >> >> -Tom >> |
From: von S. T. (G. FPI)
<Tho...@gx...> - 2002-02-05 16:38:57
|
Hello, Is this list meant to serve as a sort of "cocoon-users-newbie" list? -Tom |
From: Phil B. <ph...@tc...> - 2002-01-15 03:34:31
|
Hi again, I think I could be the only one here... so I'll do my best to answer my own questions. :) Have fun, Phil |
From: Phil B. <ph...@tc...> - 2002-01-15 02:56:56
|
Hi again, The point of the last email was to determine how I can reference logicsheets using the resource:// scheme. I've got the file:// scheme working fine. The problem with the file:// scheme is that we have several developers working on different machines and file:// would need to be different for each setup, and different again for deployment. I want to get around that problem. Thanks again, Phil |