Re: [Chello-users] JDK 1.4.0, Tomcat 4.0.4b2 and Cocoon 2.1-dev

[<cca...@ya...>]

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