>Correct me if I'm wrong here, but... >I found TC4.0 + C2.0 the most easy-to-install combination. Most users have problem >not with >installation itself, but with building of cocoon.war for the first time. Some users >have >platform-secific issues (buggy JDK 1.3.1 implemetation under Linux which crashes, etc)
Well, looking at the mailling list I suppose there are cocoon'ers that would like to argue with you ;-) For me it was much easier to install c2 on tomcat 3.x and resin.... And no matter what the reason for that might be (particularities cocoon release/ servlet engine release, build errors, buggy jdk, other platform spec.) I guess that would be a good idea to put up several preconfigured installations, which is a long and tested practice at jboss (i actually am subscribed at the jboss user list and they have much less traffic comming about the install issues). We could save time and patience for many new users and event attract new ones with this user-friendly feat. I could myself setup several configs, its just a matter of storing them somewhere - of course apache.org/cocoon2 would be reasonable. waiting for your proposals/RT's Alfredas Vadim Gritsenko wrote: >>From: Alfredas Chmieliauskas [mailto:[EMAIL PROTECTED]] >>Sent: Tuesday, October 02, 2001 8:29 AM >>To: [EMAIL PROTECTED] >>Subject: [Proposal] C2 + tomcat 4 >> >> >>Hello, >>It seems that c2 + tomcat4 is the most problematic issue for a couple of weeks >already >>(while it is one of the most used configurations). I myself had a hard time >installing >>it due to sitemap_xmap.java did not re-compile, well whatever. >> > >The funny thing that it's the most easiest combination, comparing to Tomcat 3.x, >Resin, etc. The only thing you need to do is: > - do not use JDK1.4, > - do not use CLASSPATH > - do not use /ext/ libraries > - copy cocoon.war under tomcat/webapps and restart container. > >Correct me if I'm wrong here, but... >I found TC4.0 + C2.0 the most easy-to-install combination. Most users have problem >not with >installation itself, but with building of cocoon.war for the first time. Some users >have >platform-secific issues (buggy JDK 1.3.1 implemetation under Linux which crashes, etc) > >Vadim > >>So my proposal is that it might be reasonable to bundle the next stable c2 release >together >>with tomcat in one install package (already preconfigured and working!) - like it is >done with >>jboss (+ tomcat or +jetty). >>This might be usefull for the great majority of non-dev users that do not need the >option >>to build c2 themselves, and rather spend less time on determining/quessing the /lib >location. >> >>What do you think? >> >>Alfredas >> >> >> >> >>--------------------------------------------------------------------- >>Please check that your question has not already been answered in the >>FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> >> >>To unsubscribe, e-mail: <[EMAIL PROTECTED]> >>For additional commands, e-mail: <[EMAIL PROTECTED]> >> > >--------------------------------------------------------------------- >Please check that your question has not already been answered in the >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > >To unsubscribe, e-mail: <[EMAIL PROTECTED]> >For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
